Greg King <[EMAIL PROTECTED]> (Mi 09 Apr 2008 08:13:51 CEST): > > > Heiko Schlittermann > > The normal check_host_alive command is ping, but it might not work for some > hosts like firewalls, etc. For these hosts use NMAP to scan for an open TCP > port on the host (ssh or http ports are frequently open), then create a > check_host_alive2 that does a check_tcp to that known open port, and override > the default check_host_alive for the hosts in question, or create a new group > for these hosts and use the new check_host_alive2 command.
Yep. Thank you. This possibility I know, I was just irritated from/by
(?) the logic behind the host checks. But thanks to all answers now I
understand the reason for triggering a host check as soon as *any*
service fails. (That doesn't mean that I agree with this logic, but I
understand it ;-))
Best regards from Dresden
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann HS12-RIPE -----------------------------------------
gnupg encrypted messages are welcome - key ID: 48D0359B ---------------
gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B -
signature.asc
Description: Digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________ 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
