RE: Help diagnosing NIS breakage ?

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 ?

Thanks everyone.

---------------------------------------
Robin P. Blanchard
Systems Integration Specialist
Georgia Center for Continuing Education
fon: 706.542.2404 <|> fax: 706.542.6546
---------------------------------------


> -----Original Message-----
> From: Daniel Eischen [mailto:eischen_at_vigrid.com] 
> Sent: Monday, July 14, 2003 8:57 AM
> 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:
> 
> > Ok...Been systematically stepping through the sources to locate the 
> > point at which NIS became broken.  Here are the results:
> > 
> > -CURRENT src date       report
> > -------------------     -------
> > 2003.06.18.00.00.00     success
> > 2003.06.25.00.00.00     success
> > 2003.06.26.00.00.00     success
> > 2003.06.27.00.00.00     sucesss
> > 2003.06.28.00.00.00     failure
> > 2003.07.01.00.00.00     failure
> > 2003.07.09.00.00.00     failure
> > latest (last night)     failure
> > 
> > So, something between 27 and 28 June resulted in this NIS breakage. 
> > Hopefully this will jog someone's memory and give ideas as 
> to my/our 
> > next step as to diagnosing/repairing what's wrong here. I 
> have a test 
> > box with src's and obj 's from both 27 and 28 june availabe for 
> > testing, should someone like to ssh in and poke around.
> 
> Try backing out rev 1.82 of src/lib/libc/gen/getpwent.c.
> 
> If that works, then perhaps there is something wrong
> with FreeBSD's yp_master (on server end).
> 
> -- 
> Dan Eischen
> 
>