From owner-freebsd-questions@FreeBSD.ORG Mon Oct 11 07:40:58 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 6C1AC16A4CE for ; Mon, 11 Oct 2004 07:40:58 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 202FE43D31 for ; Mon, 11 Oct 2004 07:40:58 +0000 (GMT) (envelope-from wbierman@gmail.com) Received: by mproxy.gmail.com with SMTP id 80so124855rnk for ; Mon, 11 Oct 2004 00:40:44 -0700 (PDT) Received: by 10.38.8.80 with SMTP id 80mr1129300rnh; Mon, 11 Oct 2004 00:40:44 -0700 (PDT) Received: by 10.38.179.66 with HTTP; Mon, 11 Oct 2004 00:40:44 -0700 (PDT) Message-ID: Date: Sun, 10 Oct 2004 21:40:44 -1000 From: William Bierman To: freebsd-questions@freebsd.org In-Reply-To: <2b5f066d04101019464826540b@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <2b5f066d04101019464826540b@mail.gmail.com> Subject: Re: NIS issue 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: Mon, 11 Oct 2004 07:40:58 -0000 > I may be misunderstanding what you are saying here, but master.passwd > on the slave servers should never get "updated" with NIS information. > That line that goes at the end tells the authentication process to > look to NIS for further information...same goes with the line that > goes in the group file. To test that NIS is working correctly, try > using ypcat on a client/slave server to see if it can pull the maps > from the primary server. If that doesn't work, I may be able to shed > some other light on your problem. (as usual, just include any error > messages) ypcat 'works' in the sense that it displays information, but the information it displays is old, and not synchronous with the master server. This is only the case for master.passwd, however. ypcat passwd shows the correct information (thus things that use passwd rather than master.passwd; ie finger work fine). Because of this, there really is no error message to include. Hope that is more specific, and I appreciate your assistance. (sorry, Brian if you get this twice. I didn't realize there was no Reply-to to redirect my message to the list) Regards, Bill