Date: Thu, 01 Apr 2004 17:12:57 +0200 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: "Jacques A. Vidrine" <nectar@FreeBSD.org> Cc: Sean McNeil <sean@mcneil.com> Subject: Re: nss_ldap broken Message-ID: <406C3179.2040007@fillmore-labs.com> In-Reply-To: <20040401143627.GA60225@madman.celabo.org> References: <Pine.GSO.4.10.10404010804250.29968-100000@pcnet5.pcnet.com> <406C217A.8080102@fillmore-labs.com> <20040401143627.GA60225@madman.celabo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jacques A. Vidrine wrote: > On Thu, Apr 01, 2004 at 04:04:42PM +0200, Oliver Eikemeier wrote: > >>Daniel Eischen wrote: >> >> >>>On Thu, 1 Apr 2004, Oliver Eikemeier wrote: >> >>[...] >> >>>>- it should be documented somewhere (bsd.port.mk gives you only >>>>PTHREAD_LIBS) >> >>As far as I understand the problem, every application that doesn't link to >>pthreads, but uses a library that does crashes on -CURRENT. Am I right >>there? > > 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... > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?406C3179.2040007>