> -Original Message-
> From: Marc Powell [mailto:m...@ena.com]
> Sent: Wednesday, October 07, 2009 4:13 PM
> To: nagios List
> Subject: Re: [Nagios-users] The reason of commands.cfg.
>
>
> On Oct 7, 2009, at 12:35 PM, Albert Shih wrote:
>
> > Le
On Oct 7, 2009, at 12:35 PM, Albert Shih wrote:
> Le 05/10/2009 à 13:34:30-0400, Noel Platzke a écrit
> Thanks for you answer.
>
>
>> Say we have a bunch of servers that need multiple checks that do an
>> HTTP GET on
>> different URIs and look for a specific string in the response.
>> Isn't i
Le 05/10/2009 à 13:34:30-0400, Noel Platzke a écrit
Thanks for you answer.
> Say we have a bunch of servers that need multiple checks that do an HTTP GET
> on
> different URIs and look for a specific string in the response. Isn't it easier
> to maintain a single command that takes a few argumen
Say we have a bunch of servers that need multiple checks that do an HTTP GET
on different URIs and look for a specific string in the response. Isn't it
easier to maintain a single command that takes a few arguments than having
to constantly define a new command that does basically the same thing fo
Hi all,
I would like to known why (just the historic reason) in nagios we split the
definition of the macros and the definition of a service ? For example :
When we want to monitor a pop service we create
define command {
command_namecheck_pops
command_line/usr/lib/nagio
