| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This
| allows you to choose whether the so called "rebuild rules" should be
| enabled or disabled. With AM_MAINTAINER_MODE([enable]), they are
| enabled by default, otherwise they are disabled by default. In the
| latter case, if you have AM_MAINTAINER_MODE in configure.ac, and run
| `./configure && make', then make will *never* attempt to rebuild
| configure, Makefile.ins, Lex or Yacc outputs, etc. I.e., this
| disables build rules for files that are usually distributed and that
| users should normally not have to update.
|
| The user can override the default setting by passing either
| `--enable-maintainer-mode' or `--disable-maintainer-mode' to
| configure.
|
| People use AM_MAINTAINER_MODE either because they do not want their
| users (or themselves) annoyed by timestamps lossage (see CVS), or
| because they simply can't stand the rebuild rules and prefer running
| maintainer tools explicitly.
[ https://www.gnu.org/software/automake/manual/automake.html ]
|
|
The old name has been deprecated years ago. The Autoconf documentation
says:
| Previous versions of Autoconf promoted the name configure.in, which is
| somewhat ambiguous (the tool needed to process this file is not
| described by its extension), and introduces a slight confusion with
| config.h.in and so on (for which `.in' means "to be processed by
| configure"). Using configure.ac is now preferred.
[ https://www.gnu.org/software/autoconf/manual/autoconf.html ]
|
|
Signed-off-by: Davide Madrisan <davide.madrisan@gmail.com>
|
|
Currently, there doesn't seem to be a way to configure Travis CI to omit
the Clang build on the coverity/* branches.
See: https://github.com/travis-ci/travis-ci/issues/1975
|
|
Modify the "branch_pattern" for the Coverity add-on so that it also
matches "coverity/master" and "coverity/maint".
|
|
thats because check_procs verifys there is a user for a
given uid filter. So even we use sample data for this
test, we still need a real user.
Signed-off-by: Sven Nierlein <Sven.Nierlein@consol.de>
|
|
This seems to result into more problems in the wild then before 'fixing' it
Closes Debian #739254
Reopen Debian #734811
|
|
|
|
Use two spaces for indentation.
|
|
Have Travis CI send build failure and recovery notifications to the
team@ list.
|
|
Run Coverity Scan builds on Travis CI, but only when pushing into the
"coverity" branch.
|
|
|
|
[skip ci]
|
|
just keeped 'make' in script target
|
|
|
|
|
|
|
|
Remove unnecessary whitespace in Makefile.am
|
|
|
|
|
|
|
|
|
|
check_snmp becomes capable of evaluating negative values properly,
but it might be returning CRITICALs where it used to return OK and was ignored,
if a negative value turns out to actually be a valid value.
If negative values are valid, this can be worked around,
by adding "~:" to the warning/critical threshold : 100 -> ~:100
|
|
Next commit will work on fixing these!
|
|
|
|
C89 doesn't allow variable declarations to be intermingled with code.
|
|
This change saves us from having to link check_dig against "libm"
|
|
which is already set to 10 seconds
|
|
When a timeout value is specified with the -t option, dig will sometimes
timeout before the timer is actually reached.
The problem occurs because the check_dig plugin does not pass the specified
timeout value to dig, leaving dig to timeout with it's default value which
seems to be around 10-15seconds.
To reproduce:
time ./check_dig -H 127.0.0.2 -l www.google.com -t 30
It will not run for 30secs, which is the expected behaviour.
The following will work, because the timeout is less than the default dig
timeout, so the plugin cancels the dig command:
time ./check_dig -H 127.0.0.2 -l www.google.com -t 2
This fix passes the timeout value to dig, and sets the number of retries which tends to vary from system to system by default.
Closes #1168
|
|
|
|
Adding nullmailer support to check_mailq submitted by Luca Corti
Closes: #740
Closes: #1189
|
|
|
|
|
|
|
|
Check_swap used to allow no swap when thresholds were only specified in
percent. This is no longer the case and the state now must be specified
explicitly. The default is to always return CRITICAL when the swap is
absent regardless of thresholds.
|
|
Also use strcasecmp imported from gnulib for simplicity
|
|
|
|
|
|
Return 0% free instead of 100% free when total swap is 0
|
|
Clarifying in the help output that we need either a device or mount point
listed by the mount(8) command.
(Closes: #1118)
(Closes: #1170)
|
|
Also default to "-u test -ptest" which are default MySQL accounts only
missing the prescribed privileges.
The database is no longer specified as it is not used.
If wanted is should be its own parameter/tests.
|
|
Add ability to read from options file to check_mysql_query.c
|
|
|
|
|
|
The change has also been updated in
https://www.monitoring-plugins.org/doc/state-retention.html
|
|
The NPTest.cache cannot be loaded when empty, and this prevents
getting the data and populating the file. This patch skips the file when
empty as if it didn't exist.
|
|
If a plugin still has suid privileges at the time np_enable_state() is
called, the MP_STATE_DIRECTORY environment will be ignored.
There is no need for a NEWS entry as no suid plugins use np_enable_state
yet.
|
|
|
|
Rename NAGIOS_PLUGIN_STATE_DIRECTORY to MP_STATE_DIRECTORY
|
|
Patch to provide for a -i | --ignore-missing option. This allows files that
don't exist to be monitored for without causing an error. The use case is:
* one process periodically pushes files to an "input" queue for a second
process
* the second process, when running cleanly will "consume" (process and remove)
these files
So the conditions to meet are:
1. If the file doesn't exist, that's fine (OK)
2. If the file exists, but is less than X seconds, that's fine (OK)
3. If the file exists, but greater than X seconds, no good (CRITICAL)
Since now check_file_age doesn't permit this behavior, as a non-existent file
is considered CRITICAL.
Test case was contributed by our lovely Holger.
Closes #1181, Closes #989, Closes #862, Closes #1187, Closes #845
Closes Debian Bug #496307
|
