check_ping -- how to get -i <interval> option ?

Andreas Ericsson ae at op5.se
Wed Feb 2 01:22:34 CET 2005


Minkov, Ross wrote:
> 
>>My workaround right now is to use "check_ping -t 10 -w 3000.0,80% -c
>>5000.0,100% -p 1", and to specify "max_check_attempts  30" so that i
>>know that a host is definitely down for at least 5 minutes before I
>>get a HOST DOWN alert.
> 
> 
> The way I solved similar problem ( I'm not saying this is the right way
> ;-) ) was to modify the check-host-alive command definition as follows:
> 
> # 'check-host-alive' command definition
> define command{
>         command_name    check-host-alive
>         command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w
> 3000.0,80% -c 5000.0,100% -p 10
>         }
> 
> This kind of achieves the same... Instead of sending one ping and
> waiting for 10 seconds for a response (-t 10) I send 10 pings... Not
> sure which way is better...
> 

check_icmp is better, since it won't take as long when the host is up 
and will thus make your Nagios installation perform a whole lot better 
when service checks fail.

> Regards,
> Ross
> 

Btw. I noticed you're a HP employee. Are you familiar with the HP 
Testdrive program? I'd like to get my hands on a HP-UX 11i running on 
PA-RISC 2 for NRPE development and testing. Would you be able to fix that?

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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





More information about the Users mailing list