I suppose you could then do something like
define service{
host_name <hostgroup_name>, !<server1>, !<server2>
..
}
That might check all the hosts except the 2 you exclused by !
Kai
PS: untested, I don't check services on hostgroups.
On 1/27/06, Toto Capuccino <[EMAIL PROTECTED]> wrote:
> but that's another story mate ;)
>
> 2006/1/27, Don Lewis <[EMAIL PROTECTED]>:
> > Of course then if you wanted a certain host not to have that service
> > monitored you would have to remove it from the group which in turn would
> > remove it from anything else that is being monitored on it..;)
> >
> > -Don
> >
> > On Fri, 2006-01-27 at 11:33 +0100, Toto Capuccino wrote:
> > > yes there is you create a houstgroup in hostgroups.cfg and then put
> > > the hostgroup name in services.cfg
> > >
> > > define service{
> > > ....
> > > hostgroup_name v240_servers
> > > ..
> > > }
> > >
> > >
> > > 2006/1/27, Alberto <[EMAIL PROTECTED]>:
> > > Is there any way to define services for a hostgroup something
> > > like...
> > >
> > > define service{
> > > ....
> > > host_name v240_servers
> > > ..
> > > }
> > >
> > > and not having to specify all hosts everytime I define a new
> > > service
> > >
> > > define service{
> > > host_name node1,node2,node4,...
> > > }
> > >
> > >
> >
> >
>
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
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
