This patch fixes the regular expression for the array recovery
completion percentage to detect the percentage when there is more than
one space between between "recovery =" and the percentage. (When
the percentage is less than 10%, /proc/mdstat shows it left-padded
with an extra space: "recovery =  7.6%".)
Merge pull request #18 from abradley/recoverypct

Bugfix: Detect array recovery percentages < 10% in check_linux_raid.pl
Update plugins/check_disk.c

CRITCAL -> CRITICAL typo
Merge pull request #19 from gvarisco/patch-1

Update plugins/check_disk.c
Don't prepend "^Inst" or append a space to the "include", "exclude", or
"critical" regular expressions. Instead, check for lines beginning
with "Inst" using strncmp and apply the regular expressions only when
such lines are found.

Fixes Debian bug #522812, along the lines suggested by the bug
submitter, Justin T Pryzby.
Fix SourceForge bug 1904965 - check_apt: SECURITY_RE is not correct

For the default security upgrade detection regular expression, match
"Debian-Security" in package description when it's anywhere after the
first parenthesis (not just the second space-delimited word). For
example:

... (4.0.1-5.4 Debian:6.0.6/stable, Debian-Security:6.0/stable ...
Tests for check_apt

Add a hidden "--input-file" option to check_apt (modelled on
check_procs) so that it can take files with sample apt output as input.

Add tests for my SECURITY_RE fix (debian3) and for the include, exclude
and critical options.
Allow for configuring OpenSSL

Let OpenSSL load its configuration file.  See the OPENSSL_config(3) man
page for details.

(Suggested by Max Kosmach in Debian bug report #689960, forwarded by Jan
Wagner.)
Added additional documentation to the check_range function
NEWS: Mention the OPENSSL_config(3) support
Make check_snmp backwards compatible in how it parses thresholds

Once upon a time, check_snmp used to accept inverse ranges in the
format of '2:1' to mean "alert if value is inside this range".

Since commit 7cb3ae09334796f3b54e4e6438e38c2cc679b360, ranges such
as those have instead triggered the error "Range format incorrect"
and resulted in an UNKNOWN warning state. This patch attempts to
fix the situation so that the old-style ranges continues to mean
exactly what the once did and people with lots of snmp checks can
avoid a bazillion false positives from their environments.

Signed-off-by: Andreas Ericsson <ae@op5.se>
lib/utils_base.c: Stop dumping core on bad args to check_snmp

Since the state patch introduction, we've been freeing uninitialized
memory in lib/utils_base.c::np_cleanup(), which caused coredumps
with check_snmp when illegal threshold ranges (for example) were
passed, or when we called 'die' without having read any state.

This patch fixes it by replacing the malloc() calls in there (all of
them, since using malloc() is almost always an error) with calloc().

malloc() either doesn't initialize the memory at all, or taints it
with a special marker so it can tell us when we're free()'ing memory
that hasn't been initialized. calloc() explicitly initializes the
allocated memory to nul bytes, which is a zero-cost operation when
we get the memory from the kernel (which alread does that) and almost
always desirable everywhere else.

Signed-off-by: Andreas Ericsson <ae@op5.se>
plugins/check_snmp: Show snmp error when we fail to parse its output

Dying without a hint of what went wrong is just plain annoying. With
this patch we at least get a hint.

While at it, we fix the string offset so the output we're interested
in doesn't keep the equal sign that snmpget prints.

Signed-off-by: Andreas Ericsson <ae@op5.se>
Add scripts that update man pages in drupal
Update  tools

- fix sfwebcron (tool updating sf developer guidelines)
- remove obsolete snapshot script
Update NEWS for bd78299 - check_snmp reverse ranges fix
Fix sfwebcron probe file

The initial file was created in the user's home and later tested in the
doc directory. Instead, just rsync if the file is missing.

Also add some temporary files to gitignore/make clean
check_procs: Use the range/threshold support functions from libnagiosplug.

This adds support for @<range> and makes stuff a bit simpler by removing code
duplications.

Note: Previously, the compatibility code for 'check_procs <warn> <max>'
accepted something like 'check_procs -w 10:-1 -c 10:-1 20 50' as well
(treating it as if '-w 10:20 -c 10:50' was specified). This is no longer the
case ... additional arguments are only used as warn/crit thresholds in case
-w/-c is not specified at all.
check_procs: Added performance data to plugin output.
check_procs: Remove superfluous newline character