Thanks for the clarification. On Nov 9, 2007 9:50 AM, Marc Powell <[EMAIL PROTECTED]> wrote: > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:nagios-users- > > [EMAIL PROTECTED] On Behalf Of Jerad Riggin > > Sent: Friday, November 09, 2007 9:44 AM > > To: Giles Coochey > > Cc: [email protected] > > Subject: Re: [Nagios-users] Service scheduling > > > > I currently have the normal check at 10 minutes, max attempts at 1, > > and retry intervals at 1. > > This means that nagios will check the service every 10 minutes until > there is a problem, then it will perform 1 check 1 minute later and send > a notification if it's still in a non-OK state. All future checks return > to the 10 minute interval, even if it's still in a non-OK state. > retry_check_interval is only used up to max_check_attempts. > > -- > Marc > > ------------------------------------------------------------------------- > 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 >
------------------------------------------------------------------------- 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
