monitoring-plugins/plugins, branch release-1.4.16

check_tcp: Print performance data even with -D

2012-06-27T15:29:11Z

When using the 1.4.15 release of the Nagios Plugins, a command such as check_tcp -H pop.example.com -p 995 -D 14 usually produced two lines of output, e.g.: OK - Certificate will expire on 12/13/2014 23:59. TCP OK - 0.009 second response time on port 995|time=0.008849s;;;0.000000;10.000000 The second line was removed by 4d06603060fc1233861b164870f0d3a2e0d8d2eb. However, as the old two-line output is a valid (though in this case unintended) way to spit out performance data, removing the second line might break current setups. Therefore, we revert to the old behaviour, at least for the moment. The issue was reported by Jochen Bern on the "nagiosplug-devel" mailing list (Message-ID: <4FEAE812.8030309@LINworks.de>).

check_snmp: use single quotes for perf data labels

2012-06-26T22:02:09Z

Fix performance data label containing spaces in check_snmp (Jochen Bern)

2012-06-26T18:53:13Z

Add --perf-oids option for check_snmp to retain optional 1.4.14 compatibility

added test case for certificate checs with both warning and critical values

2012-06-25T10:54:15Z

check_http: added test for warning thresholds

2012-06-25T10:53:47Z

fixed typo in sslutils

applied patch that adds both critical and warning thresholds to certificate expiration checks of check_tcp, check_http, check_smtp

2012-06-25T10:05:16Z

check_ping: Add missing newline to die() calls

2012-06-24T23:58:17Z

Our die() function expects the caller to append the trailing newline character.

Merge remote-tracking branch 'github/waja/master'

2012-06-24T23:14:12Z

Conflicts: NEWS

check_ping: Ignore ping(1)'s exit status

2012-06-24T13:51:56Z

Don't return a WARNING state if the number of lost packets is greater than zero but below the specified warning threshold. This happened because the check_ping plugin used the exit status of the ping(1) utility. (#3535140 - Tobias Brox)

Fix check_by_ssh test for non-Bash login shells

2012-06-22T15:11:18Z

In the C shell and in the Z shell, the "?" character must be quoted or backslash-escaped in order to use it verbatim. Therefore, a command such as check_by_ssh -H test.example.com -l joe echo huh? might fail, depending on joe's login shell on test.example.com. Just to make sure, this commit removes most punctuation characters from our test strings.