[Nagios-devel] passive checks and check_command
Posted: Fri Oct 10, 2003 5:30 am
Hi,
I have gone through the docs, faqs and both the users and the devel
groups, and have this question:
Nagios requires that "check_command" exists in any defined service. With
passive services, a "check_command" is an anomaly, as the checking is really
done by the main engine at the specified command_check_interval in the
main config file.
Setting the check_command to "" (ie, a blank raw command line) is one way
to circumvent the requirement, but this is not mentioned explicitly in the
docs. Is this correct, and more importantly, why have such a requirement
in the first place with passive services?
Tielman de Villiers
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
I have gone through the docs, faqs and both the users and the devel
groups, and have this question:
Nagios requires that "check_command" exists in any defined service. With
passive services, a "check_command" is an anomaly, as the checking is really
done by the main engine at the specified command_check_interval in the
main config file.
Setting the check_command to "" (ie, a blank raw command line) is one way
to circumvent the requirement, but this is not mentioned explicitly in the
docs. Is this correct, and more importantly, why have such a requirement
in the first place with passive services?
Tielman de Villiers
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]