Hey Dave,
Thats the way I have things set up:
define service{
use generic-service
hostgroup_name *,!switch,!router
service_description SSH
check_command check_ssh
}
Works perfectly fine for me..
-----------------------------------
Jeffrey Lensen
System Administrator Hyves
hyves page: http://skyler.hyves.nl
mail/msn: [EMAIL PROTECTED]
dave stern - e-mail.pluribus.unum wrote:
> I'm trying to streamline my nagios config using wildcards.
> Unfortunately, not all services I wish to define via wildcard
> follows a clean set of rules. Is it possible to define a service
> with a host list of something like *,!linux1, !linux2
>
> I suspect the answer is no and what I'd need to do is use
> a combination of hostgroups and hosts eg
> define service {
> hostgroup unix, ultrix, sco
> service_description ....
> }
> define service {
> host_name host1, host2, host3, host4
> ...
> }
>
> Anyone find a way around this?
> TIA
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> 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
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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
