Higher check frequency (Was: Re: nagios archives in var/archives)

[Florian.Kirchmeir at infineon.com]

Hi!

I wouldn't bother changing the default interval or even hacking the
source to support high-frequency check intervals.
Just make the service passive, and write some simple script to run
continously, pinging your host(s) every x seconds and submitting results
as passive service checks.

Regards,
Florian Kirchmeir

	-----Original Message-----
	Date: Mon, 14 Jun 2004 22:44:29 +0200
	From: Andreas Ericsson <ae at op5.se>
	To: nagios-users at lists.sourceforge.net
	Subject: Re: [Nagios-users] Re: nagios archives in var/archives

	Cook, Garry wrote:
	> Never tried this, don't know if it will work, but what if you
left your
	> default interval set to 60 seconds, and then changed your
service check
	> interval to '.25'?
	> 
	> -g
	> 

	I'm chopping on it, adding some code that makes it read the
extentions 
	s, m and h (with m being default) for seconds, minutes and
hours, 
	respectively.

	It's terribly slow going though, since I've got about a dozen
other 
	projects at hand simultaneously.

	> nagios-users-admin at lists.sourceforge.net wrote:
	> 
	>>This started happening when I modified my nagios.cfg's
	>>interval from the
	>>default 1 minute to 15s. The reason I brought it down is for
getting
	>>ping response every 15s. I will restore it back to 60 but, is
	>>there a way to have
	>>a service check be in the interval of 15s even if our default
	>>is 60 seconds?
	>>
	>>Thanks.



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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