> -----Original Message----- > From: Andreas Ericsson [mailto:a...@op5.se] > Sent: Thursday, September 27, 2012 3:08 PM > To: Nagios Users List > Cc: Frost, Mark {BIS} > Subject: Re: [Nagios-users] Using "contacts" in host definition -- Bug ?
> On 09/26/2012 09:25 AM, Frost, Mark {BIS} wrote: >> I believe this is a "feature" introduced in 3.3 or thereabouts. I've >> always found it very irritating and wish there was some way to turn >> off inheriting host contacts/contactgroups to services as it's never >> what I want. >> > It's a half misfeature. The intention was (and is) that services with no > contactgroups OR contacts should inherit the ones from the host, but it > was coded up so that if the service had contactgroups (but not contacts) > it would inherit contacts (but not contactgroups) from the host. The same > applied when the service had contacts but no contactgroups and the host > had contactgroups. > In 4.0 this is fixed so only services with neither contacts nor contact- > groups inherit them from the host. > -- > Andreas Ericsson andreas.erics...@op5.se I still see that as a misfeature. I would rather have the preflight check tell me there's an error because I forgot to define contacts for the service than for it to assume that what I want is anything to be inherited from a host definition. I'd be OK if that were the default behavior and was configurable, but I'd be the first to disable that in nagios.cfg if it were a configurable preference. Yeah, I know, patches gleefully accepted :-). Mark ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ 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