Service / Host dependencies

[Jay Chandler]

Taylor Dondich wrote:
> Kind of defeats the purpose, doesn't it?  The normal process is, even
> if a host is up, the services it provides could be dead in the water.
> I don't think you really want this, but instead, if you want to give
> the service check more time to determine if a problem is REALLY a
> problem, increase the max_check_attempts of the service in question,
> giving Nagios more time to check the service to really change it's
> state to a HARD state.  Read up on different states and how they work
> at:
>
> http://nagios.sourceforge.net/docs/3_0/statetypes.html
>   

You're right-- I wasn't clear.  I still want to know if the services 
die, but in the event that the services die because the host is dead, 
I'd rather get a single "host down" message instead of eight "X Service 
on $HOST isn't working" messages.

-- 
Jay Chandler / KB1JWQ
Living Legend / Systems Exorcist
Today's Excuse: Just type 'mv * /dev/null'


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