> > Am I missing something fundamental about this command ? > > It appears that you missed the 'min:max' vs. 'max:min' thing on the ranges, > but 1) that's a common oversight, and 2) it doesn't appear to be the real > reason you're getting nothing but warnings.
James, thanks for all this detailed explanation on check_snmp. I am using the plugin extensively, but I have a fundamental problem with it being designed to give an OK if checks for warning and critical ranges and are within that range. This has for me - and must for others - been the source of confusion and need for some brain strain. What do you suppose was the thinking with this approach? The man page says it best. -w, --warning=INTEGER_RANGE(s) Range(s) which will not result in a WARNING status Why not specify the *warning* range using the *warning* option that *WILL* produce a *warning*? It just seems all backwards. -- - Kyle --------------------------------------------- [EMAIL PROTECTED] http://www.panix.com/~kylet --------------------------------------------- ------------------------------------------------------- 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&kid=110944&bid=241720&dat=121642 _______________________________________________ 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