Date: Thu, 3 Jan 2008 10:55:28 -0500 From: Vivek Khera <vivek@khera.org> To: freebsd-stable@freebsd.org Subject: Re: Nagios + 6.3-RELEASE == Hung Process Message-ID: <2D5923AA-F9C3-490A-8016-F4B3BCCCA4AF@khera.org> In-Reply-To: <738861275EBE2BF6D27F547B@ganymede.hub.org> References: <59DD6CCE263ECD75A7283A7B@ganymede.hub.org> <477A72B8.8010307@protected-networks.net> <477BAD2B.8070603@tomjudge.com> <1DB78354-EBA2-43D0-A2D6-EFDA4950135B@netleader.com.au> <477C1629.1030604@tomjudge.com> <20080103104129.T36551@wallace.netleader.com.au> <738861275EBE2BF6D27F547B@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 2, 2008, at 8:26 PM, Marc G. Fournier wrote: >> My gut feeling is that it's not an architecture issue but more an >> interoperability issue between the Nagios threading code and the >> libpthread() >> threading library. > > As noted in my original report, this isn't a nagios issue per se ... > my first > experience with this issue was with Azureus/java ... so its a > 'threading issue > in general' ... For years now I've been running with libthr as the default threading library as set in libmap.conf. The *only* issue I've run into is with Java, and that requires libpthread. So my libmap.conf looks like this, and everything works really well (including Nagios, mysql, etc.) --cut here-- # use libthr instead of pthread lib libpthread.so.2 libthr.so.2 libpthread.so libthr.so # JDK HotSpot compiler fails randomly with libthr. [java] libpthread.so libpthread.so libpthread.so.2 libpthread.so.2 --cut here--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2D5923AA-F9C3-490A-8016-F4B3BCCCA4AF>