From owner-freebsd-questions  Sun Dec 14 11:24:59 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA02115
          for questions-outgoing; Sun, 14 Dec 1997 11:24:59 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from milkyway.org (lta-r-1.usit.net [205.241.194.17] (may be forged))
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA02088
          for <freebsd-questions@FreeBSD.ORG>; Sun, 14 Dec 1997 11:24:51 -0800 (PST)
          (envelope-from toby@milkyway.org)
Received: (from toby@localhost) by milkyway.org (8.8.5/8.8.3) id OAA00725; Sun, 14 Dec 1997 14:23:31 -0500 (EST)
Date: Sun, 14 Dec 1997 14:23:30 -0500 (EST)
From: Toby Swanson <toby@milkyway.org>
To: Tom <tom@sdf.com>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: NIS login problem
In-Reply-To: <Pine.BSF.3.95q.971213195541.26297A-100000@misery.sdf.com>
Message-ID: <Pine.BSF.3.91.971214140843.531A-100000@antares.milkyway.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Sat, 13 Dec 1997, Tom wrote:

> 
>   You shouldn't run yppasswdd on clients.  It should only run on the
> master NIS server.
> 

Killed it.

> 
>   Do you have "+:::::::::" in master.passwd on the client?
> 

Well, uh, sort of. :^)  What I had was from the O'Reilly NFS and NIS book.

+:*::::::::

Their reason was to prevent the user "+" from logging in with no password 
if NIS is not running.  It seems the use of a shadow password file takes 
care of this problem.  When I changed it logins started working.

Thanks for your help.

Toby