To be fair, one situation where these wildcard template dependencies
don't work is when you want to define a number of dependent services
that rely on a service on the same host (i.e. not a number of separate
services on different hosts that rely on a single (or wildcardable)
host/service).
I re-wrote my entire config tree with templates at one point, only to
find it was wasted effort (in my situation) as I have large numbers of
hosts/services all relying on others within the same host, not a single
point elsewhere... so they aren't expressible that way. So I've still
got megabytes of config files to generate when there's a change, vs. the
idea of changing a simple template and having it propagate :(
/eli
Hugo van der Kooij wrote:
On Thu, 16 Mar 2006, Matthew Joyce wrote:
I check a lot of window services from linux via snmp.
One service is SNMP, if this fails or stops, others will fail.
An I going to get a heap of notification for each service ?
I've looked at the service dependency section in the docs, and it looks
like I need to define a dependency for each service, for each host.
That's a lot of defining.
Not at all. Read the archives for samples of how to use the wildcards in
your dependencies definitions.
Hugo.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
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
