On Fri, Nov 5, 2010 at 3:49 PM, RT <r...@ragweed.net> wrote: > Using: Nagios Version 3.2.2 > Can check_nrpe be convinced (or hacked) to exit UNKNOWN rather than CRITICAL > on `Connection Refused`? Is there a way to accomplish this without having to > modify check_nrpe's source directly?
Not that I know of. I have gotten around this by writing a "filter" script that is used as a wrapper for check_nrpe in some cases. The filter calls check_nrpe with the supplied arguments and (as defined by a config file) does a regex match to see if it should change the return code. If so, it returns the new return code (UNKNOWN in your case). Otherwise, it returns whatever check_nrpe returned. -- HTH, YMMV, HANW :) Jason The path to enlightenment is /usr/bin/enlightenment. ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ 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
