monitoring-plugins, branch release-1.4.15Monitoring Plugins
https://www.monitoring-plugins.org/repositories/monitoring-plugins/atom?h=release-1.4.152010-07-27T20:45:20Z1.4.15 prep2010-07-27T20:45:20ZTon Voonton.voon@opsera.com2010-07-27T20:45:20Zurn:sha1:e546a084afd62af8e5fcd8bfbd9d9c757a6b90e9Merge branch 'master' of ssh://tonvoon@nagiosplug.git.sourceforge.net/gitroot/nagiosplug/nagiosplug2010-07-14T13:22:51ZTon Voonton.voon@opsera.com2010-07-14T13:22:51Zurn:sha1:4bb8e2f51481338f7381b48186502519863399aaAdded text re: MD5SUM updates in nightlies, but tarballs not2010-07-14T13:22:04ZTon Voonton.voon@opsera.com2010-07-14T13:22:04Zurn:sha1:9bab433981f6c67b40776d1916baae28a0243124Fix --help output when MAX_OIDS is altered.2010-07-09T23:39:09ZThomas Guyot-Sionnestdermoth@aei.ca2010-07-09T23:28:44Zurn:sha1:2527bdd4b67e4a347d620b10e3b9f8b6e54de30cFix examples in check_disk, where it implied was possible to suffix unit values to warn/crit parameters2010-07-07T10:03:24ZTon Voonton.voon@opsera.com2010-07-07T10:03:24Zurn:sha1:02f9207ebe3a5ae5b35b4b69be1f3bf95ab5a220Allow check_ifstatus to accept version=2c2010-07-07T08:56:21ZTon Voonton.voon@opsera.com2010-07-07T08:56:21Zurn:sha1:0205c7c0cfc5ba182f2cb675d1df4de72f13c9e2Fix cmd_run overwriting the environment2010-07-02T16:55:19ZThomas Guyot-Sionnestdermoth@aei.ca2010-07-02T16:55:19Zurn:sha1:cf2bcf6c7afa8eb7a54e01f98a9998a7e1ac0852
Some commands need the environment to function properly. One such
example is check_ssh and check_by_ssh when a SOCKS proxy is required.
This patch use setenv and extern char **environ to alter and pass the
new environment to the child process Those modules have been added to
Gnulib for portability.
Import the environ module from gnulib (86ba51)2010-07-02T16:36:08ZThomas Guyot-Sionnestdermoth@aei.ca2010-07-02T16:34:55Zurn:sha1:6b6051606175d870bb45bbe67866c1643d4d964agit-notify: Be careful with "--no-merge"2010-07-02T13:28:35ZHolger Weissholger@zedat.fu-berlin.de2010-07-02T13:28:35Zurn:sha1:319e308521e0e460fe0b06ee093248628dda819d
The "-X" option (which asks git-notify to not report merge commits) was
implemented by setting the "--no-merge" option on each invocation of
git-rev-list(1). However, we do not only use git-rev-list(1) to get the
list of new commits, but also to check whether the old branch head (or
tag) is a parent of the new branch head (or tag). For this latter
check, the "--no-merge" option should not be set; otherwise, git-notify
would be fooled to believe that the branch has been rewritten if the old
head was a merge commit.
Corrected rate_multiplier calculation2010-06-30T13:16:32Ztonvoonton.voon@opsview.com2010-06-30T13:16:32Zurn:sha1:5c72d075deb12239e2f1c61cf7b91e0f6ef19640