Date: Mon, 22 Aug 2005 11:36:23 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-hackers@freebsd.org, lists@nbux.com Subject: Re: nagios and freebsd threads issue : help please ... Message-ID: <Pine.GSO.4.43.0508221130550.28532-100000@sea.ntplx.net> In-Reply-To: <20050822.080938.95905450.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Aug 2005, M. Warner Losh wrote: > So there's something in the list, I've gone through and done a call > tree analysis to show the extensive and pervastive nature of the > functions that nagios calls after fork. I don't know if these are all > problems or not, since I don't know if some of these functions might > be called before the first thread is created with pthread_create. > However, any that are called after that clearly have undefined > behavior. Note that we (David Xu and myself) took a different approach to handling fork() in libpthread (and probably libthr) than was done in libc_r. We thought it better not to try and reinitialize libpthread (and to some extent libc) because it is messy and to expose non-portable applications. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0508221130550.28532-100000>