Date: Tue, 30 Mar 2004 08:16:31 -0600 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: Sean McNeil <sean@mcneil.com> Cc: freebsd-current@freebsd.org Subject: Re: nss_ldap broken Message-ID: <20040330141631.GH10949@lum.celabo.org> In-Reply-To: <1080639464.81872.3.camel@server.mcneil.com> References: <1080334840.11426.12.camel@server.mcneil.com> <Pine.GSO.4.10.10403261747480.16871-100000@pcnet5.pcnet.com> <20040330023247.GA5637@madman.celabo.org> <1080614678.52004.5.camel@server.mcneil.com> <20040330030243.GB5757@madman.celabo.org> <1080639464.81872.3.camel@server.mcneil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 30, 2004 at 01:37:44AM -0800, Sean McNeil wrote: > On Mon, 2004-03-29 at 19:02, Jacques A. Vidrine wrote: > > Thanks! So, could you try the patch below? I think it is now > > basically identical with what you posted, except for the changes to > > nss_compat.c. > > After making a bone-head mistake and just installing the libc after a > make update (duh!) I finally managed to salvage my system and give the > patch a go. Things look good. Thanks! I'll commit it. > I'm still concerned that nss_atexit can cause a seg11 if a nss_*.so.1 > starts up any threads when the program isn't threaded otherwise. Don't > really know why an nss plugin would want to do that, but it is > hazardous. The locks may not be needed regardless. Dan, how do threads interact with atexit()? Are threads serialized at that point? Does the main thread call all the atexit handlers? Cheers, -- Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040330141631.GH10949>