From notifications at github.com Thu May 1 21:25:01 2014 From: notifications at github.com (abrist) Date: Thu, 01 May 2014 12:25:01 -0700 Subject: check_ntp_peer - Added specific state output for each metric. It now sho... (#1239) In-Reply-To: References: Message-ID: Tests changed with: https://github.com/nagios-plugins/nagios-plugins/commit/9e587a9587cf9abefa2edeb88da5093ae070fcf7 -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1239#issuecomment-41946544 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Tue May 13 11:07:57 2014 From: notifications at github.com (Sven Velt) Date: Tue, 13 May 2014 02:07:57 -0700 Subject: check_apt: Please output package names to update (#1256) Message-ID: Just a list of packages which cause WARN(updates)/CRIT(security updates) status as multiline output could be very helpful. THX -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/issues/1256 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Tue May 13 12:11:36 2014 From: notifications at github.com (waja) Date: Tue, 13 May 2014 03:11:36 -0700 Subject: check_apt: Please output package names to update (#1256) In-Reply-To: References: Message-ID: Hi Sven, there seems consense that check_apt need more work (see https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1031680). Anyways as this is an upstream project, we are waiting for patches / code from downstream to move to libapt-pkg or something similar. I think it doesn't make sense to work on minor issues as long as we have to port all the stuff later. Cheers, Jan. -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/issues/1256#issuecomment-42938054 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat May 17 07:21:36 2014 From: notifications at github.com (gcoxmoz) Date: Fri, 16 May 2014 22:21:36 -0700 Subject: Fixing check_tcp to return desired exit code (#1257) Message-ID: https://github.com/monitoring-plugins/monitoring-plugins/issues/1062 A simple little patch to return an accurate statement ("Connection refused") along with the desired return code when asked to do so. The global exit code is being passed around as a functional return code, and so the state of the actual connection function is being lost/interpolated badly upstream. You can merge this Pull Request by running: git pull https://github.com/gcoxmoz/monitoring-plugins master Or you can view, comment on it, or merge it online at: https://github.com/monitoring-plugins/monitoring-plugins/pull/1257 -- Commit Summary -- * Update check_tcp.c * Update netutils.c * Patch against issue 1062 -- File Changes -- M plugins/check_tcp.c (2) M plugins/netutils.c (12) -- Patch Links -- https://github.com/monitoring-plugins/monitoring-plugins/pull/1257.patch https://github.com/monitoring-plugins/monitoring-plugins/pull/1257.diff -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1257 -------------- next part -------------- An HTML attachment was scrubbed... URL: