Hosts.cfg question, service configuration ques tion, ldapv3

[jeff vier]

On Tue, 2003-11-18 at 16:00, Quanah Gibson-Mount wrote:
> >> 1) In the hosts.cfg file, it allows you to specify a check command to
> >> I see no way to configure how *often* you want this command to be  
> >> executed.   
> > nagios is "smart" about it.  this is in the docs.  
> Define "smart".  If any service on the host is down, the host itself
> appears to be marked down.  This is not an accurate assessment of the
> problem.  Example: I turned off the ldap service on an ldap system.  The
> service detail view correctly shows that the service is down.  The host
> detail view incorrectly says the host is down.  The host itself is fine.

Mine doesn't do that at all.  One service down just shows as that
service being down, nothing more.

> >> 2) In the service.cfg file, it seems I have to define the same
> service
> > either use the hostgroup_name, or a comma separated list of hosts.  
> This is an undocumented feature of the service function then?  

I guess so.  I just looked in the FAQs, and it's not in there, either. 
Huh.  I have no idea where I picked this up.

Notably.  No spaces.  machinea,machineb,machiney,machinez

> >From the docs:  
> host_name: This directive is used to specify the short name of the host
> that the service "runs" on or is associated with. 
> 
> There is no hostgroup_name directive listed, nor does it say that you
> can comma separate this list. 

Yeah, that's wrong. :)



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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