From owner-freebsd-current@FreeBSD.ORG Mon Jul 14 05:59:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9DA737B401; Mon, 14 Jul 2003 05:59:44 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D88A43FE1; Mon, 14 Jul 2003 05:57:07 -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 h6ECv4AI021708; Mon, 14 Jul 2003 08:57:04 -0400 (EDT) Date: Mon, 14 Jul 2003 08:57:04 -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: "Jacques A. Vidrine" cc: current@freebsd.org cc: John De Boskey Subject: RE: Help diagnosing NIS breakage ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 12:59:45 -0000 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