Making passive checks notify like activechecks--race condition?

[Morris, Patrick]

> We want our passive checks to notify like active checks.  
> What if we make a plugin which does nothing but report the 
> current state (and description) of a service?  Define it like 
> this in checkcommands.cfg:
> define command{
>     command_name   repeater
>     command_line   $USER1$/repeater_homebrew $SERVICESTATEID$ 
> $SERVICEOUTPUT$
> }
> 
> and the plugin itself is brain dead:
> --------------------
> #!/bin/sh
> 
> exit=$1
> shift
> 
> echo $*
> exit $exit
> --------------------
> 
> We run this plugin as an *active* check so that we get the 
> notification behavior we want and then a passive check to 
> actually check the service and submit results.


I'm not sure what you're trying to accomplish here, but passive checks
*do* notify like active checks.

Maybe you just need to set max_check_attempts to "1" in your service
definition?

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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