"No response" result code inconsistency in nagios-plugins

[Ian Chard]

Hi,

There seems to be a general inconsistency in how "no response"
conditions are handled in some of the plugins.  For example:

	check_snmp		UNKNOWN
	check_nt		CRITICAL
	check_ifoperstatus	WARNING

I would have thought that a plugin should return UNKNOWN if nothing
is received unless it's the response itself that's being tested (i.e.
check_ping should obviously return CRITICAL if no packets are received).

Do Nagios folk agree, and if so, is it worth logging this as a bug?

Cheers
- Ian

-- 
Ian Chard, Unix & Network Administrator   |  E: ian.chard at sers.ox.ac.uk
Systems and Electronic Resources Service  |  T:  80587 / (01865) 280587
Oxford University Library Services        |  F:          (01865) 242287


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
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