Date: Mon, 14 Jul 2003 14:16:10 -0400 From: "Robin P. Blanchard" <Robin.Blanchard@gactr.uga.edu> To: <deischen@freebsd.org>, <stable@freebsd.org> Subject: RE: Help diagnosing NIS breakage ? Message-ID: <EE3D3FBAFFCAED448C21C398FDAD91AC2374A3@EBE1.gc.nat>
next in thread | raw e-mail | index | archive | help
In our implementation, the NIS server is ActiveDirectory with ServicesForUnix 3.0 :) > -----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 > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EE3D3FBAFFCAED448C21C398FDAD91AC2374A3>