no max check attempts for host checking?

[Mark Frost]

Hello.  I have something that's not working the way I'd expect.

We are monitoring services on windows hosts and as is common practice,
not explicitly checking the host state.  Wehn the host gets rebooted, I
expect that a service might fail, then Nagios would attempt a host
check.  I would like the host check to not alert on a single ping
failure, but rather hold off for say 5 failures before it sends an
alert.  The intent is to not get an alert if the box is just being 
rebooted.

I've set the following for my test host:

max_check_attempts 10
check_interval 0
retry_interval 1
active_checks_enabled no


Our configuration is a distributed one so the distributed node has
obsession turned on, but the central node does not.

When testing, we find that no matter what I set the max_check_attempts
to, an alert is sent on the first ping failure.

Is there something I'm missing?

Thanks

Mark




-------------------------------------------------------------------------
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 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