Date: Mon, 20 Jun 2005 16:56:36 -0400 (EDT) From: Charles Sprickman <spork@fasttrackmonkey.com> To: hackers@freebsd.org Subject: Nagios and threads Message-ID: <Pine.OSX.4.61.0506201654400.374@gee5.nat.fasttrackmonkey.com>
next in thread | raw e-mail | index | archive | help
Hello, Just curious if there's any regulars here who would like to help Ethan out: http://nagios.sourceforge.net/docs/2_0/whatsnew.html "Known Issues There are a few known issues with the Nagios 2.0 code at the moment. Hopefully some of these will be fixed before 2.0 is released as stable... 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. Some folks from Yahoo! have reported that using the pthread library causes Nagios to pause under heavy I/O load, causing some service check results to be lost. Switching to linuxthreads seems to help this problem, but not fix it. The lock happens in liblthread's __pthread_acquire() - it can't ever acquire the spinlock. It happens when the main thread forks to execute an active check. On the second fork to create the grandchild, the grandchild is created by fork, but never returns from liblthread's fork wrapper, because it's stuck in __pthread_acquire(). Maybe some FreeBSD users can help out with this problem." Thanks, Charles
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSX.4.61.0506201654400.374>