Date: Wed, 22 Jun 2005 08:53:00 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: deischen@freebsd.org Cc: spork@fasttrackmonkey.com, hackers@freebsd.org, kamalp@acm.org, peadar.edwards@gmail.com Subject: Re: Nagios and threads Message-ID: <20050622.085300.82192668.imp@bsdimp.com> In-Reply-To: <Pine.GSO.4.43.0506221027490.22792-100000@sea.ntplx.net> References: <34cb7c8405062207246b582eaf@mail.gmail.com> <Pine.GSO.4.43.0506221027490.22792-100000@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050622.085300.82192668.imp>