hosts.cfg and ping question

[Julie Catellier]

When I first set up Nagios, I was able to set the check_command to 
check-host-alive and everything worked well.  Now, the initial 
hosts that I set up in hosts.cfg automatically ping for the host 
without any entry in the 'check-command' and I am not able to 
check-host-alive in any new host entries.  Is there any entry that 
overrides the hosts.cfg configuration?  Below is an example.  The 
imap1 entry does not check-host-alive.  The smtp3 entry 
automatically pings the host.  I also double checked that 
check-host-alive does work for these hosts from the command line. 
Any Ideas?

# 'smtp3' host definition
define host{
        use                     its-host                ; Name of 
host template to use
        host_name               smtp3.x.x.x
        alias                   VUmail: Mail Transport server
        address                 xx.xx.xx.xx
        }
# 'imap1' host definition
define host{
        use                     its-host                ; Name of 
host template to use
        host_name               imap1.x.x.x
        alias                   VUmail: Personal mailbox server
        address                 xx.xx.xx.xx
        check_command           check-host-alive
        notification_interval   120
        notification_period     24x7
        max_check_attempts      10
        }

---------------------------------------
Julie Catellier
Vanderbilt University
Information Technology Services
Email: julie.catellier at Vanderbilt.Edu



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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