Date: Thu, 1 Apr 2004 09:32:24 -0600 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: Oliver Eikemeier <eikemeier@fillmore-labs.com> Cc: Sean McNeil <sean@mcneil.com> Subject: Re: nss_ldap broken Message-ID: <20040401153224.GC60392@madman.celabo.org> In-Reply-To: <406C3179.2040007@fillmore-labs.com> References: <Pine.GSO.4.10.10404010804250.29968-100000@pcnet5.pcnet.com> <406C217A.8080102@fillmore-labs.com> <20040401143627.GA60225@madman.celabo.org> <406C3179.2040007@fillmore-labs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 01, 2004 at 05:12:57PM +0200, Oliver Eikemeier wrote: > Jacques A. Vidrine wrote: > >No. Problems only occur if run-time loading/unloading via > >dlopen/dlclose is used, and then only if a lock or other thread > >library data structure might be held ``across'' the load or unload. > >So I think it is a rare, but troublesome, condition. > > It hit apache 1.3.29 + php4 too (PR 64932), which should be a pretty > common combination. Before my change slapd + Berkeley DB where > affected... Interesting. Perhaps a different but equally bad side-effect. > >When you changed the way OpenLDAP was linked, this condition occurred > >within libc due to dynamic loading of nss_ldap. So, lots of people's > >working systems suddenly starting crashing after upgrading. > > I'm sorry about that. Slapd was crashing, which is somewhat important > for the OpenLDAP port. This seemed like the proper fix to me, see the > recent thread `fix for libpthread' on -current. At least it fixed slapd :P Sorry, didn't mean to sound accusatory. I just meant to highlight the fact that the current system is fragile. 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?20040401153224.GC60392>