Date: Wed, 22 Jun 2005 21:48:13 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: spork@fasttrackmonkey.com, hackers@freebsd.org, kamalp@acm.org, peadar.edwards@gmail.com Subject: Re: Nagios and threads Message-ID: <Pine.GSO.4.43.0506222146570.25618-100000@sea.ntplx.net> In-Reply-To: <20050622.085300.82192668.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 22 Jun 2005, M. Warner Losh wrote: > In message: <Pine.GSO.4.43.0506221027490.22792-100000@sea.ntplx.net> > Daniel Eischen <deischen@freebsd.org> writes: > : We do protect the malloc lock across a fork(), but that's it. > > With 4.x libc_r, you could easily get hangs accross a fork() if you > did anything before the exec (like setup fd's for stdin/out). This > was due to internal libc_r state being inconsistant. I was only referring to libpthread in the above... I don't think libc_r is as robust in that regard. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0506222146570.25618-100000>