Date: Tue, 21 Jun 2005 15:26:36 +0200 From: Michal Mertl <mime@traveller.cz> To: Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?= <des@des.no> Cc: Charles Sprickman <spork@fasttrackmonkey.com>, hackers@freebsd.org Subject: Re: Nagios and threads Message-ID: <1119360396.781.17.camel@genius1.i.cz> In-Reply-To: <86slzcos9q.fsf@xps.des.no> References: <Pine.OSX.4.61.0506201654400.374@gee5.nat.fasttrackmonkey.com> <86slzcos9q.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote: > Charles Sprickman <spork@fasttrackmonkey.com> writes: > > 1. FreeBSD and threads. On FreeBSD there's a native user-level > > implementation of threads called 'pthread' and there's also an > > optional ports collection 'linuxthreads' that uses kernel hooks. > > This is only the case for FreeBSD 4. FreeBSD 5 has native threads. Yes, the description on Nagios page is not precise but unfortunately Nagios still has some problems even on 5.4. I wasn't able to find out what was wrong and the problem dissappeared when I had to replace the computer with single-processor one. The symptoms I observed were that every several days one Nagios process was consuming all the CPU doing hundreds of thousands of syscalls per second. It got always stuck around the time when the the daily cron job run. I did a ktrace on the stuck process and tried to abort it to have the core but I've lost the ktrace output and it never saved the core :-(. I'll install it on another machine and try to diagnose the problem some more. Michal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1119360396.781.17.camel>