From owner-freebsd-current@FreeBSD.ORG Fri Mar 26 12:40:24 2004 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 6778316A4CE; Fri, 26 Mar 2004 12:40:24 -0800 (PST) Received: from ms-smtp-02-eri0.socal.rr.com (ms-smtp-02-qfe0.socal.rr.com [66.75.162.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43DE743D31; Fri, 26 Mar 2004 12:40:24 -0800 (PST) (envelope-from sean@mcneil.com) Received: from mail.mcneil.com (cpe-24-24-233-222.socal.rr.com [24.24.233.222])i2QKeLSa013928; Fri, 26 Mar 2004 12:40:21 -0800 (PST) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 02879FD152; Fri, 26 Mar 2004 12:40:21 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73897-02; Fri, 26 Mar 2004 12:40:20 -0800 (PST) Received: from [24.24.233.222] (mcneil.com [24.24.233.222]) by mail.mcneil.com (Postfix) with ESMTP id 857A6FD12E; Fri, 26 Mar 2004 12:40:20 -0800 (PST) From: Sean McNeil To: "Jacques A. Vidrine" In-Reply-To: <20040326125934.GA68357@madman.celabo.org> References: <1080273717.18231.10.camel@server.mcneil.com> <20040326125934.GA68357@madman.celabo.org> Content-Type: text/plain Message-Id: <1080333620.9866.4.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 26 Mar 2004 12:40:20 -0800 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-current@freebsd.org Subject: Re: nss_ldap broken 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: Fri, 26 Mar 2004 20:40:24 -0000 On Fri, 2004-03-26 at 04:59, Jacques A. Vidrine wrote: > Hmm, it does seem that there is an error situation where that could > be the case, but the problem description above doesn't follow from > that case. The patch will fix it. (The situation would occur if > /etc/nsswitch.conf existed, but was not readable.) > > > Does anyone have any insight into what this might be? I would love to > > have it working again. > > I will try to reproduce here. So far no luck. Interesting!!! Not what I had thought was going on. I compiled libc with symbols and I get this: #0 0x28214800 in ?? () #1 0x2816be35 in nss_atexit () at /usr/src/lib/libc/net/nsdispatch.c:518 #2 0x2818e9db in __cxa_finalize (dso=0x0) at /usr/src/lib/libc/stdlib/atexit.c:184 #3 0x2818e6fc in exit (status=672827136) at /usr/src/lib/libc/stdlib/exit.c:69 #4 0x08049b68 in free () at /usr/src/lib/libc/stdlib/malloc.c:1153 #5 0x08049279 in free () at /usr/src/lib/libc/stdlib/malloc.c:1153 So even though the write lock didn't cause a crash the unlock did. I didn't try your patch as it looked like the locks were being appropriately handled. Here is the real odd part: passwd: ldap files group: ldap files works (no seg 11)!! passwd: files ldap group: files ldap fails (seg 11)!! Cheers, Sean