-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 24 Sep 2008 16:05:39 -0500, Marc Powell <[EMAIL PROTECTED]> wrote:
> >On Sep 24, 2008, at 12:33 PM, Jennifer Cranfill wrote: > >> The only setting for service check timeout that I see is the global >> service_check_timeout setting. Is there a setting that can be applied >> per command or per service check? >All standard plugins support a timeout parameter, typically '-t ><seconds>' that you can pass in the command definition. Run '/path/to/ >plugin --help' to see if it's supported and usage. It could also be >passed from a service definition as a $ARGx$ macro. I think you missed the request. nagios.cfg has a config option, 2 actually, service_check_timeout and host_check_timeout. They're independent of the -t <seconds> option that most plugins support. It's the "end of life" for the plugin, nagios uses it to kill a plugin. The -t option allows the plugin to report a failed state if the response doesn't come back within a certain time. The service_check_timeout allows nagios to report when a plugin hasn't responded within a certain time. >From what I can tell, it cannot be customized per plugin. However, if you set it high enough to cover all the plugins, and then set sane values for the -t option for the plugins you should be okay. - -- Jon Angliss -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) - GPGshell v3.64 iEYEARECAAYFAkja0+cACgkQK4PoFPj9H3NzjACgnMR9fTwb28dYEFUYL+LeIJKJ X4QAoMAFEPu5PGJp5YlDEG1YZwT5GtuD =zgR8 -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Nagios-users mailing list Nagios-users@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
