Host check timing

[David Dyer-Bennet]

I'm monitoring some far-away remote hosts, that we connect to via the
public internet (well, there's an encrypted VPN involved).  I'm trying not
to send notifications until an outage persists for a while.

In an example I looked at this morning, I see that it was repeating the
host check every 10 seconds until it hit the retry count.

Where does that 10 seconds time come from?  The manual is remarkably vague
about host check scheduling; about all it says is that it does them on
demand, and "If the first host check returns a non-OK state, Nagios will
keep pounding out checks of the host until either (a) the maximum number
of host checks (specified by the max_attempts option in the host
definition) is reached or (b) a host check results in an OK state."

Does this mean I have no control over the timing?  Can I treat the 10
second observed delay as real (and then control total time delay by
setting max_attempts high)?

(Running Nagios 2.12 on Centos 5).
-- 
David Dyer-Bennet, dd-b at dd-b.net; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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