On 6/19/07, Jonathan Call <[EMAIL PROTECTED]> wrote:
No.
I was forced to implement a distributed model and limit the service
checks to less than 1000 on a server. Even then I still have to run a
cron job that checks for nagios children than are spinning on the CPU as
a result of this fork issue.
I've found that somewhere after 1500+ service checks there will be a
random weekly event that causes almost a hundred nagios checks to hit
this fork issue all at the same time and promptly tank the FreeBSD
server.
Any chance you could post what your cron script looks like? I might
replicate it here if a solution can't be found. Also, has anyone contacted
the port maintainer? It seems silly to include something in the port tree
that is broken. I'm also considering watching the log file to see if it's
been updated w/i the past 5 minutes or something like that (read: ugly).
--
Kyle Sexton
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
