[Nagios-devel] Re: passive checks and check_command

[Jasmine]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 13 October 2003 17:51, tvilliers wrote:
> Thanks Stanley --
>
> With this:
> > However, there is a benefit in having a legitimate command defined for a
> > passive service in that service states that cannot otherwise be reset,
> > can be reset by scheduling the passive service check with a command like
> > 'ping'.
>
>  ... I presume that the passive service has the "check_freshness" option
> enabled -- as this is the only way that the "check_command" will actually
> execute (at the stated "freshness_threshold" time).
>
> So let me rephrase then: why is a "check_command" required for a passive
> service which does not check for freshness?
>
>
> Tielman de Villiers
>

Hi

The "check_command" is still required for a passive service definition because 
in any service definition template, that option is compulsory. But, that 
"check_command" for the passive service is not actually executed by Nagios at 
all because it is passive. It will only be executed when the freshness option 
is being enabled. Hope this helps. 

Warmest Regards,
Jasmine Chua


SecureCiRT Pte Ltd
Blk 750C Chai Chee Road
#04-01 Technopark at ChaiChee
Singapore 469003
Tel: 6243 6800 DID: 6243 6805
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/ioNFNgvTa7Hj2AURAkicAKCMN5BIOFxk598iZEvHj2vhw0lC+QCdG9GG
6Ra2w51S/7v5rdTTltXpYgo=
=DDcd
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
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