Date: Wed, 02 Jan 2008 10:53:38 -0500 From: "Brian A. Seklecki" <lavalamp@spiritual-machines.org> To: Tom Judge <tom@tomjudge.com> Cc: "Marc G. Fournier" <scrappy@hub.org>, jarrod@netleader.com.au, freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Nagios + 6.3-RELEASE == Hung Process Message-ID: <1199289218.2774.9.camel@soundwave.pitbpa0.priv.collaborativefusion.com> In-Reply-To: <477BAD2B.8070603@tomjudge.com> References: <59DD6CCE263ECD75A7283A7B@ganymede.hub.org> <477A72B8.8010307@protected-networks.net> <477BAD2B.8070603@tomjudge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2008-01-02 at 15:26 +0000, Tom Judge wrote: > Michael Butler wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 I'm pretty sure that he's getting ready to ship 3.0 release w/ broken threading on FreeBSD. I haven't had time to test it on NetBSD yet, but since it can be fixed by switching up which threading engine you link against on the Free* side of *BSD, its likely a long-term fix in Ports instead of polluting the code with #IFDEF's for FreeBSD-specific POSIX thread nits (it's a hard-sell since the same code works fine on Solaris and Linux w/o issue) What we need is: 1) Nightly builds of Nagios against various releng trees 2) Serious BSD involvement in the project to look at the threading code (beyond me) 3) Bug tracking on the Nagios side I recently proposed #1 and #2 on nagios-user@, but I got a lot of push-back from Andreas. Any type of professional project management improvements that quote "Aren't fun" are heavily frowned upon. ~BAS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1199289218.2774.9.camel>