From owner-freebsd-questions@FreeBSD.ORG Tue Oct 12 02:49:10 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 729DE16A4CE for ; Tue, 12 Oct 2004 02:49:10 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26EC543D49 for ; Tue, 12 Oct 2004 02:49:10 +0000 (GMT) (envelope-from wbierman@gmail.com) Received: by mproxy.gmail.com with SMTP id 80so172704rnk for ; Mon, 11 Oct 2004 19:49:01 -0700 (PDT) Received: by 10.38.179.17 with SMTP id b17mr1451769rnf; Mon, 11 Oct 2004 19:49:00 -0700 (PDT) Received: by 10.38.179.66 with HTTP; Mon, 11 Oct 2004 19:49:00 -0700 (PDT) Message-ID: Date: Mon, 11 Oct 2004 16:49:00 -1000 From: William Bierman To: freebsd-questions@freebsd.org In-Reply-To: <2b5f066d041011044746110d4e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041010.235204.4f07a9c7ff46fcd5.10.0.3.20@bugsgrief.net> <2b5f066d041011044746110d4e@mail.gmail.com> Subject: Re: NIS issue (now resolved!) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: William Bierman List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2004 02:49:10 -0000 > Interesting...something that pops into my mind is something obvious > since it was stated in the handbook, but needs to be said > anyway...when you add stuff to the master.passwd file, do you re-make > the database? Also, if you follow the directions in the handbook, > they suggest you make a different master.passwd file in /var/yp to > store the accounts that go into nis....I re-wrote the make file > section for passwd.* and told it to look to /etc/passwd where the UID > is greater then 1000....and it works great for me...if you'd like a > copy of the entries in the Makefile, I'll send them to you. It sounds > like that's what's going on (and I've had endless students make this > mistake in class as well...it's a common one). I solved the problem! It turns out there were other machines on the network which somehow or another turned themselves into slave servers, and were propogating the old information. I did rm -rf /var/yp/cluster on all of them, and rebooted them all, and now it works. Thanks for your assistance, Brian! Bill