Define dependencie in service defs?

[Assaf Flatto]

Litwin, Matthew wrote:
> On Jun 21, 2010, at 10:03 AM, Assaf Flatto wrote:
>
>   
>> Litwin, Matthew wrote:
>>     
>>> Is there a way to define  what service a service depends on within te  
>>> service definition itself for cases where the dependency heirarchy is  
>>> localized to the same host? Dependency definitions are terrific in  
>>> that they are so flexible, but it would be nice to contain that  
>>> functionailty within a single service definition in an effort to  
>>> simplify configuration.
>>>
>>>       
>> At the moment you must define it in a separate definition , but it does 
>> not have to be in a separate file .
>> just put the service dependency definition below/above the service 
>> declaration and thus you have a more "easy to maintain" way to know what 
>> you set up and how you need it .
>>     
>
> Thanks, that is actually a good and simple solution. I suppose if I employ the regular expression matching tool for configuration that would make it even more automated. Have you worked with that. It seems pretty new.
>   
I have not worked with the regex tool ,

But i must say i am pretty "old Fashioned " in  the way i like my Nagios 
configuration - extremely readable to the novice and following the KISS 
policy.

Let us know how it worked for you .

-- 
Never,Ever Cut A Deal With a Dragon 


I am doing a Charity Bike ride On the 27 of June for the
Capital to Coast Charity. Please help by Donating
http://www.justgiving.com/Lovefilm-capital-to-coast



------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
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