Zabbix is an enterprise-class open source distributed monitoring solution.
Zabbix is software that monitors numerous parameters of a network and the
health and integrity of servers. Zabbix uses a flexible notification
mechanism that allows users to configure e-mail based alerts for virtually
any event. This allows a fast reaction to server problems. Zabbix offers
excellent reporting and data visualisation features based on the stored
data. This makes Zabbix ideal for capacity planning.
WWW: http://www.zabbix.com/
===> The following configuration options are available for zabbix24-server-2.4.8:
CURL=on: Support for web monitoring
FPING=on: Build/install fping for ping checks
IPMI=off: Support for IPMI checks
IPV6=on: IPv6 protocol support
JABBER=on: Support for Jabber media type
JAVAGW=off: Support for Java gateway
LDAP=off: Support for LDAP server checks
LIBXML2=off: Support for libxml2 (required by monitoring VMware)
NMAP=off: Build/install nmap for o/s detection
SSH=on: Support for SSH-based checks
====> Options available for the single DB: you have to select exactly one of them
MYSQL=on: MySQL database support
PGSQL=off: PostgreSQL database support
SQLITE=off: SQLite database support
ORACLE=off: Oracle database support
====> Support for database checks via ODBC: you have to select exactly one of them
IODBC=off: ODBC backend via iODBC
UNIXODBC=on: ODBC backend via unixODBC
===> Use 'make config' to modify these settings
Remove USE_SQLITE from bsd.databases.mk, replaced by USES=sqlite.
While there replace USE_SQLITE=x by USES=sqlite:x.
PR: 208971
Submitted by: mat
Exp-run by: antoine
With hat: portmgr
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D5951
- Switch to our framework's USES=execinfo
- Use EXECINFO_CPPFLAGS and EXECINFO_LDFLAGS to fix detection of
libexecinfo on FreeBSD 9.x
- Mark frontend ports as NO_ARCH
PR: 205740
Submitted by: myself
Approved by: maintainer
Remove UNIQUENAME and LATEST_LINK.
UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.
Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.
Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)
Reviewed by: antoine, bapt
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D3336
net-mgmt/zabbix2[24]-server: fix zabbix and database startup sequence
The Zabbix server and proxy ports require a database to run. They
currently support four, PostgreSQL, Oracle, SQLite, and MySQL. As
of now, rcorder puts them ahead of the database ports, so they spit
out dozens of error messages during startup and, worse, get the
database pulled out from under them during shutdown.
The ports used to provide a solution for this, by defining
ZABBIX_REQUIRE. The value of this variable used to be added to the
REQUIRE lines in the startup scripts, but this was removed accidentally
from 2.2 in r355546 and never existed in 2.4. This patch adds it
back, in a slightly different, optionsng-friendly way.
PR: 195081
Submitted by: chris@chrullrich.net
Approved by: pakhom706@gmail.com (maintainer)
Add four zabbix24 ports to net-mgmt (similar to zabbix22* ports)
This add Zabbix 2.4.1 server, agent, frontend, and proxy
PR: 194104
Submitted by: pakhom706 (gmail)
