Re: [Nagios-devel] Unable to define empty check_command
Posted: Sun Jan 08, 2006 8:38 am
On Sun, Jan 08, 2006 at 01:24:03PM +0100, Andreas Ericsson wrote:
> Dmitry Sivachenko wrote:
> >
> >I am unable to entirely leave check_command parameter in the case when
> >I derive this host definition from another which did use check_command.
> >
>
> Create another template, identical in all aspects except for the lack of
> a check_command and use that for the hosts that shouldn't have one.
>
> >I want to be able to redefine check_command to empty value.
> >
>
> You can not.
>
I see. But you suggest an ugly workaround.
The ability to redefine check_command to an empty value permits to create
much more elegant config files for nagios.
BTW, it is documented.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
> Dmitry Sivachenko wrote:
> >
> >I am unable to entirely leave check_command parameter in the case when
> >I derive this host definition from another which did use check_command.
> >
>
> Create another template, identical in all aspects except for the lack of
> a check_command and use that for the hosts that shouldn't have one.
>
> >I want to be able to redefine check_command to empty value.
> >
>
> You can not.
>
I see. But you suggest an ugly workaround.
The ability to redefine check_command to an empty value permits to create
much more elegant config files for nagios.
BTW, it is documented.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]