From owner-freebsd-questions Mon Aug 7 12: 7:21 2000 Delivered-To: freebsd-questions@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id E968D37BBAF for ; Mon, 7 Aug 2000 12:07:15 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id PAA74735; Mon, 7 Aug 2000 15:07:22 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 7 Aug 2000 15:07:22 -0400 (EDT) From: "Brandon D. Valentine" To: David Thiel Cc: freebsd-questions@freebsd.org Subject: Re: What's up with yp login authentication? In-Reply-To: <398EF5C0.F2F80ED3@nexprise.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Aug 2000, David Thiel wrote: >I'm also having some very bizarre yp problems. I've double and >triple-checked my configuration, and although I can do ypwhich and ypcat >the NIS maps, logins don't appear to authenticate through NIS. Maybe >there's something I'm missing, but I added a test user after enabling >NIS, and they didn't authenticate through it. Is there something >different one has to do when adding users under NIS? You could have had a brainfart like I did this morning. I just fixed my NIS problem. I copied the shadow file off of my IRIX NIS server without remembering to run it through awk and convert from a sixth edition passwd format to the BSD format that includes the extra fields for login classes, etc. I couldn't get it to authenticate because it was not able to read the master.passwd.byname and .byuid maps properly. Finger could get the information since it was only looking in the passwd.byname and .byuid maps. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message