Help diagnosing NIS breakage ?

Daniel Eischen eischen at vigrid.com
Mon Jul 14 11:21:30 PDT 2003


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 at vigrid.com] 
> > Sent: Monday, July 14, 2003 2:13 PM
> > To: Robin P. Blanchard
> > Cc: John De Boskey; current at 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



More information about the freebsd-stable mailing list