Date: Wed, 13 Jul 2005 14:46:58 +0200 From: Jeremie Le Hen <jeremie@le-hen.org> To: Christophe Yayon <lists@nbux.com> Cc: freebsd-hackers@freebsd.org Subject: Re: nagios and pthreads Message-ID: <20050713124658.GU39292@obiwan.tataz.chchile.org> In-Reply-To: <44776.194.51.215.62.1121257035.squirrel@webmail.nbux.com> References: <61087.192.168.42.2.1121196788.squirrel@webmail.nbux.com> <20050713095059.GS39292@obiwan.tataz.chchile.org> <44776.194.51.215.62.1121257035.squirrel@webmail.nbux.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Christophe, > Yes but if i understand, there is a bug in libc_r on FreeBSD ? libc_r indeed has some kind of bug, I don't know. Anyhow, you are using RELENG_5, so you should be using native threads with either libpthread (libkse, M:N) or libthr (1:1). I don't know what Nagios does just after fork(2), it would be worth to check. It appears that fork(2)ing without exec(2)ing or _exit(2)ing in a pthreaded program is not a "valid" behaviour, regarding to SUSv3 [1]. I don't want to avoid admitting there is a problem in FreeBSD threading library, I don't know how other OSes handle this, but Nagios folks should really avoid doing what is explicitely dissuaded in SUSv3. For now, it doesn't resolve your problem unfortunately. [1] http://www.opengroup.org/onlinepubs/009695399/functions/pthread_atfork.html (look at the "RATIONALE" section) -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050713124658.GU39292>