Why not create more generic command definitions and pass the specific arguments along to the commands in your service definitions?
http://nagios.sourceforge.net/docs/2_0/xodtemplate.html#command Andrew -----Original Message----- From: David Dyer-Bennet [mailto:d...@dd-b.net] I don't really understand the purpose / utility of the "command" level of abstraction in Nagios configuration. (2.10; we're still on Centos 4.7). To define a new service to check particular Windows web services we've written, I define a service, and then it has to refer to a command, and over in the command I have to hard-code the parameters needed to test this specific service -- so in fact I need a separate command for each service. This seems, to me, to just introduce confusion, and separate bits of information that belong together. Is this just a historical artifact that in fact doesn't make much sense, or are there lots of cases where it's useful and makes it easier or clearer to do what you want? ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ 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
