------=_NextPart_000_047B_01C6F43C.A928B430
Content-Type: multipart/mixed;
boundary="----=_NextPart_001_047C_01C6F43C.A928B430"
------=_NextPart_001_047C_01C6F43C.A928B430
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Oops! There's almost certainely a bug (I didn't experienced it but I fixed
it) when you have multiple dependency definitions where some of them are not
same-host.
After a good sleep I realised that it would make much more sense to have
host_name set and dependent_host_name unset.
So now here's the new usage.
How to use it:
Just omit both "dependent_host_name" and "dependent_hostgroup_name" entries
in a servicedependency definition. Ex:.
define servicedependency {
hostgroup_name pool1,pool2
service_description Master service
dependent_service_description Slave 1,Slave 2,Slave 3
notification_failure_criteria c,u
}
Still EXPERIMENTAL (see comment in my previous post)
Please send me any bugs/comments you have with this patch...
Thomas Guyot-Sionnest
UNIX Systems Administrator
Zango
E: [email protected]
P: 514.787.4714 | F: 514.787.4707
www.zango.com
Read our blog at http://blog.zango.com
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf
> Of Thomas Guyot-Sionnest
> Sent: October 20, 2006 1:03
> To: Nagios-Devel
> Cc: william(at)elan.net
> Subject: Re: [Nagios-devel] Service dependencies
>
> Alright! I found out I'm not that bad in C and made my own patch.
>
> What it does:
>
> When Nagios duplicate servicedependency definitions, it checks for any
> missing required variables. When it checks for empty host_name entry,
> instead of returning an error I set a flag and fill-up the
> master_hostslist
> using the dependent_host_name entry instead.
>
> Later in the "duplication" loop, if the flag is present I
> don't duplicate
> any definition that doesn't have the same hostname for master
> and dependent
> host.
>
> How to use it:
>
> Just omit the "host_name" entry in a servicedependency definition ex:.
>
> define servicedependency {
> service_description Master service
> dependent_hostgroup_name pool1,pool2
> dependent_service_description Slave 1,Slave 2,Slave 3
> notification_failure_criteria c,u
> }
>
> WARNING: This patch is EXPERIMENTAL. It was only tested with
> the expected
> configuration. I DID NOT TEST ANY NORMAL CONFIGURATION;
> NEITHER DID I TEST
> CONFIGURATION ERROR HANDLING. I'll review and test this patch
> thoughtfully
> as soon as I get some spare time.
>
> Please send me any bugs/comments you have on this patch...
>
> Thomas
>
> > -----Original Message-----
> > From: william(at)elan.net [mailto:[email protected]]
> > Sent: Thursday, October 19, 2006 22:42
> > To: Thomas Guyot-Sionnest
> > Cc: Tobias Mucke; Nagios-Devel
> > Subject: Re: [Nagios-devel] Service dependencies
> >
> >
> > On Thu, 19 Oct 2006, Thomas Guyot-Sionnest wrote:
> >
> > > I guess you mean setting it up in the service definition?
> But you'll
> > have to
> > > define which host here as well. So is't excatly the same as the
> > > servicedependency definition.
> > >
> > > Actually I'm just thinking there could be another way. What if by
> > omiting
> > > one of the host_name / hostgroup_name variable, instead
> of failling
> > check it
> > > would turn the "same host" mode.
> > >
> > > define servicedependency {
> > > service_description Master service
> > > dependent_hostgroup_name pool1,pool2
> > > dependent_service_description Slave 1,Slave 2,Slave 3
> > > same_host_dependency 1
> > > notification_failure_criteria c,u
> > > }
> >
> > Interestingly enough I made a patch (for 2.2 & 2.3) that does almost
> > exactly that. But I did not do it cleanly as I did not add
> new option
> > and changed the behavior so that:
> >
> > define servicedependency {
> > hostgroup_name group1
> > servicegroup_name master_servicegroup
> > dependent_servicegroup_name slavegro
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]