the network. If somebody can't change their config to do what they need
without allowing them to be specified, they can rebuild it themselves
and take responsibility for their own actions.
One specific case this is often used is to check disk space. Note that
you don't need to set a specific partition for check_disk, running it without
a -p flag will check all the filesystems.
https://www.monitoring-plugins.org/archive/help/2014-January/006503.html
re: name change; keeping the same directory name for now
rework multipackages to use BUILD_PACKAGES
avoid unnecessary build dependencies
merge -ntp into -main, this plugin is now a standalone C implementation
rather than a perl script depending on ntpd.org tools
a new libmysqlclient non-blocking API which utilizes co-routines. The X86
specific GCC ASM co-routine support hid the fact that there was an issue.
The only fallback code so far is POSIX user contexts which OpenBSD does not
support.
Input from and Ok sthen@ jasper@
switch back to the original version, because icinga's fork of NSCA
has been discontiued
Please note: it is recommended that NCSA-ng is used for new
installations.
ok sthen@
- remove REVISION-main
- use ${PREFIX-web} instead of /var/www in CONFIGURE_ARGS
- use --with-htmurl, --with-httpd-conf, --with-log-dir to have
(almost) identical CONFIGURE_ARGS for nagios and icinga
- make post-install block more compact
- move the apache config file snippet from nagios-main to nagios-web
- add a pkg-readme
with feedback and ok sthen@
It adds "System Board 1 LCD Cable Pres 0: Connected" to the list of
things that fall under:
"As long as Dell doesnt correct these CIM elements return code we have
to ignore it"
"sure" sthen@
fix for metacharacter filtering (CVE-2013-1362) which was letting $(...)
through, reported by a couple of people.
this loses the v6 support but the fork which added this is currently dead.
horrible Nagios NSCA passive check acceptor. Command lines are compatible
but the protocol is not - however the two servers can coexist to assist
during a migration. Fix/ok rpe@
Adds workaround for Dell PE x620 machines:
"[T]he CIM element "System Board 1 Riser Config Err 0: Connected" returned
a code of 12, which, according to the CIM documentation, means "Not
connected". But all affected users had an actual Riser Card connected
and working. So this return code does not make sense."
ok sthen@
