<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Fridtjof Busse wrote: <blockquote cite="mid20060808143522.d9fd6ac9.fbusse@gmx.de" type="cite"> <pre wrap="">* Hari Sekhon <a class="moz-txt-link-rfc2396E" href="mailto:hpsekhon@googlemail.com"><hpsekhon@googlemail.com></a>: </pre> <blockquote type="cite"> <pre wrap="">yes, the service definitions can definitely take a list like host_name host1,host2,host3... </pre> </blockquote> <pre wrap=""> That's what I'm currently doing. </pre> <blockquote type="cite"> <pre wrap="">Not sure about the macros, check the docs that come with nagios since they do mention quite a bit about this. It is likely you can define your own $MACROS$ as you want and have all the services update just be restarting the daemon. </pre> </blockquote> <pre wrap=""> Well, stuff like $USER2$ does not work for me and the docs don't mention such a setup (or I didn't find it yet). </pre> </blockquote> did you put the $USERn$ definition in a resource file and source it via nagios.cfg as follows: resource_file=/path/to/usermacros.cfg ? Apparently you are allowed 32 of these. If you can use hostgroup names instead of host names in services definition then this will be better in one way, although it will show up in your Status Overview and Status Summary pages which might mess them up a bit if you want concise overviews like public webservers, internal servers, servers at remote office etc.... -h </body> </html>