Multiple Nagios proccesses running.

[Brian Murphy]

Andreas Ericsson <ae <at> op5.se> writes:

> 
> Two methods have been suggested and prototyped.
> Either fire up the checking-threads via fork(), dup() execve() and 
> multiplex all checks, or run a separate thread (as opposed to a fork()) 
> for each check and use shared memory for inter-thread communication. 
> With some sort of limit on the number of pending check-results this 
> could be done fairly easily. Each thread could even handle the results 
> themselves, provided proper locking is in place.
> 

Are there things I could undertake in the config of this environment to deal 
with this issue?

Do I need to find a way to stop the results coming through in clumps?





-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Nagios-users mailing list
Nagios-users at 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