From owner-freebsd-stable@FreeBSD.ORG Mon Jul 14 11:21:30 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0473437B401 for ; Mon, 14 Jul 2003 11:21:30 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 631BE43F3F for ; Mon, 14 Jul 2003 11:21:29 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h6EILSAI011915; Mon, 14 Jul 2003 14:21:28 -0400 (EDT) Date: Mon, 14 Jul 2003 14:21:28 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: "Robin P. Blanchard" In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org Subject: RE: Help diagnosing NIS breakage ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 18:21:30 -0000 On Mon, 14 Jul 2003, Robin P. Blanchard wrote: > In our implementation, the NIS server is ActiveDirectory with ServicesForUnix > 3.0 :) Well, maybe it's a bug in that. I was assuming that you were using a FreeBSD NIS server. > > -----Original Message----- > > From: Daniel Eischen [mailto:eischen@vigrid.com] > > Sent: Monday, July 14, 2003 2:13 PM > > To: Robin P. Blanchard > > Cc: John De Boskey; current@freebsd.org; Jacques A. Vidrine > > Subject: RE: Help diagnosing NIS breakage ? > > > > > > On Mon, 14 Jul 2003, Robin P. Blanchard wrote: > > > > > That did it.... > > > > > > Using latest -CURRENT sources, but backing out to > > > src/lib/libc/gen/getpwent.c,v 1.81 gets NIS clients working again. > > > Re-sync this in CVS ? > > > > The change (rev 1.82) to getpwent.c allows FreeBSD NIS > > clients to work with Solaris NIS+ servers running in YP > > compatibility mode. Without the change, FreeBSD clients in > > such an environment can't log in. > > > > I think this is exposing a bug in our NIS implementation, > > but don't know enough about it to be sure. I think backing > > it out just hides the bug again. As a work-around, we > > could try yp_order first, and if that fails, try yp_master. -- Dan Eischen