For this functionality, to make it easier, you may want to make wrapper scripts which do the actual command sending to nagios, but a command parameter to that script could be the actual check command to run (the script), along with any other command parameters. That way you're not writing duplicate scripts for all your plugins.
-- Taylor Check out my Shortcut with O'Reilly Press: Network Monitoring with Nagios: http://oreilly.com/catalog/9780596528195/index.html On Fri, Aug 22, 2008 at 1:00 PM, Douglas K. Rand <[EMAIL PROTECTED]> wrote: > Taylor> So a nice round-about way of doing it would be to disable > Taylor> active checks on the service initially. Then when your > Taylor> passive check script detects a problem, not only does it send > Taylor> nagios a passive check RESULT, but it also sends a command to > Taylor> enable active checks on that service. Then your active check > Taylor> script, when it determines the problem has resolved itself, > Taylor> could also send nagios itself a command to disable active > Taylor> checks on that service. Fun way to do it. > > "Fun" Clearly a word with many meanings. :) > > Thanks for the tip, I never considered that approach. I'll give it a > shot. > ------------------------------------------------------------------------- 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
