Date: Mon, 14 Jul 2003 08:57:04 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: "Robin P. Blanchard" <Robin.Blanchard@gactr.uga.edu> Cc: John De Boskey <jwd@bsdwins.com> Subject: RE: Help diagnosing NIS breakage ? Message-ID: <Pine.GSO.4.10.10307140853560.19808-100000@pcnet5.pcnet.com> In-Reply-To: <EE3D3FBAFFCAED448C21C398FDAD91AC010837@EBE1.gc.nat>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10307140853560.19808-100000>