Unable to define empty check_command

[Dmitry Sivachenko]

On Sat, Jan 07, 2006 at 03:22:41PM -0600, Marc Powell wrote:
> 
> 
> > -----Original Message-----
> > From: nagios-devel-admin at lists.sourceforge.net [mailto:nagios-devel-
> > admin at lists.sourceforge.net] On Behalf Of Dmitry Sivachenko
> > Sent: Saturday, January 07, 2006 9:25 AM
> > To: nagios-devel at lists.sourceforge.net
> > Subject: [Nagios-devel] Unable to define empty check_command
> > 
> > Hello!
> > 
> > We are using nagios 2.0b6.
> 
> [chop]
> 
> > 
> > define host {
> > name h2
> > check_command
> > <...>
> > register 0
> > }
> > 
> > And nagios reports:
> > 
> > # nagios -v nagios.cfg
> > 
> > Nagios 2.0b6
> > Copyright (c) 1999-2005 Ethan Galstad (http://www.nagios.org)
> > Last Modified: 11-14-2005
> > License: GPL
> > 
> > Reading configuration data...
> > 
> > Error: Could not add object property in file
> > '/usr/local/etc/nagios/templates.cfg' on line 21.
> > 
> > .....
> > 
> > 
> > Is it possible to allow one to define empty check_command to disable
> check
> > for host health as described in the manual?
> 
> Leave out the check_command entirely --
> 
> define host {
> name h2
> <...>
> register 0
> }
> 
> Note that by specifying 'register 0' you are telling Nagios that this is
> a template to be applied against a real host definition and not an
> actual host definition itself. That really doesn't make much sense when
> you specify a 'name' parameter.
> 


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.

I want to be able to redefine check_command to empty value.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click