On Wed, Oct 15, 2008 at 3:31 AM, Andreas Ericsson <[EMAIL PROTECTED]> wrote: > No. Nagios forks after (optionally) caching the plugin in memory, > bringing the embedded perl stuff with it. The child runs the cached > plugin. The saving is entirely in avoiding to load /usr/bin/perl > each and every time a plugin is run (at the slight expense of copying > some more memory at every fork if epn is compiled in).
Thank you, Andreas, I really appreciate your answer. I will go back to the drawing board to try to figure out what I am doing wrong then that is causing 135 checks to not complete in less than 5 minutes .. avg check time is 4 sec, avg check latency is .04 secs, so not sure what I am doing wrong. the machine is powerful enough to have dozens of checks run at the same time, but so far I only see Nagios forking one child at a time. I have interleave set to 's' and intercheck delay set to .5 and large_installation_tweaks at 1 and still only one fork at a time, which is what lead me to falsely think that ePN checks were treated differently. So now that i know otherwise, back to the drawing board to figure out what I messed up. > Multiplexing would be the way to go. It's the most complex, but the > most portable and the least resource-hungry. Excellent. Thank you. - Max ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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
