> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Jeffry Bilder > Sent: Wednesday, March 15, 2006 11:34 AM > To: nagios-users@lists.sourceforge.net > Subject: [Nagios-users] Service Dependancies > > I am currently trying to find a way to supress emails about services > being down if PING has a problem. Does anyone else have it setup in > this manner? For example... > > A windows machine is not pingable, suppress all other notifications > until Ping is accessible again.
This is standard behavior if you have a host check_command that returns non-OK when the host is unavailable. http://nagios.sourceforge.net/docs/1_0/networkreachability.html > I am also having an issue with Plugins timing out, or being refused. Is > there a setting in nagios to increase the # of checks it can run > simultaneously? http://nagios.sourceforge.net/docs/1_0/configmain.html#max_concurrent_ch ecks You'll probably be interested in the *_timeout settings there as well. These control the maximum amount of time allowed for each type of action. Bear in mind that each plugin typically has its own timeout value as well. You can see what those are and how to change them by running 'plugin_name --help' and modifying the command definitions that call that plugin appropriately. Finally, you can run '/path/to/nagios -s /path/to/nagios.cfg' to get information about scheduling and recommendations for some settings. -- Marc ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ 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
