On 10/11/07, Marc Powell <[EMAIL PROTECTED]> wrote: > > > > -----Original Message----- > > From: Terry [mailto:[EMAIL PROTECTED] > > Sent: Thursday, October 11, 2007 1:21 PM > > To: Marc Powell > > Cc: Nagios Users mailinglist > > Subject: Re: [Nagios-users] host checking logic > > > > > command to check_dummy. Why is freshness needed for passive checks? > > It's not needed but it's a safety net in case whatever is sending the > passive checks stops doing so. Nagios would happily continue to report > the last check it received before the submission process died forever. > Freshness checking allows nagios to recognize that it hasn't seen any > recent results for that host in some configurable time and runs the > hosts check_command to be pro-active. The documentation covers some > scenarios about what that check_command can/should be. > > -- > Marc >
Ok, that makes sense. I have used passive checks in conjunction with active checks, never exclusively and don't foresee ever having that situation. :) Thanks for your help! ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nagios-users mailing list [email protected] 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
