On 32-bit systems using of intval causes 32-bit Int overflow. Also: - Fix sprintf specifiers to output float without decimal digits. - Do not check, if result of files or size calculation command (`find` or `du`) is 0: if user wants, it may specify expected size greater, than 0, and 0 result will be catched. If he doesn't - i don't care too. - Check that calculation command result contains only numbers (no dots, minus signs, etc). This ensures, that result is integer without forcing upper bound of 32- or 64-bit integers. - Explicitly cast calculation command result to float.
Requires (and is hardcoded to use) memcached on localhost:11211 as a cache.
Add --perf option to produce performance data output Output example: OK - CPU: 1min 1% 5sec 1% 1sec 1%. Memory OK (6%). Temp (A/W/C): 48.5/85.0/90.0; Fans: OK OK. PSUs: OK N/A. Up 25.91 days|CPU_1min=1%;70;90 CPU_5sec=1%;85;95 CPU_1sec=1%;95;98 Memory=6%;70;90 Temp=48.5deg;85.0;90.0
Bear the following from Jethro R Binks in mind: On Tue, 24 Jan 2012, Lutz Knabenreich wrote: > As far as I know the OID output is 0.5 Degrees Celsius each unit and not > Fahrenheit, means OID Value 160 turns to be 80 Degrees Celsius. This is generally correct these days, and has been for some years, but it is worth remembering that several times during the last 10 years the MIB has changed between reporting in units of 1 deg C and 0.5 deg C. On several occasions we found an upgrade caused our temp readings to double or half (with mild panic until we looked more closely!). Jethro.