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: https://www.zabbix.com/
===> The following configuration options are available for zabbix2-server-2.0.21_1:
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
LDAP=off: Support for LDAP server checks
NMAP=off: Build/install nmap for o/s detection
SSH=off: 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 expired ports:
2018-10-09 net-mgmt/zabbix2-server: End of Life was August, 2017
2018-10-09 net-mgmt/zabbix2-agent: End of Life was August, 2017
2018-10-09 net-mgmt/zabbix2-frontend: End of Life was August, 2017
2018-10-09 net-mgmt/zabbix2-java: End of Life was August, 2017
2018-10-09 net-mgmt/zabbix2-proxy: End of Life was August, 2017
Add Zabbix Java Gateway ports
This update separates Java Gateway componentes from the Zabbix Server port,
creating an additional slave port for each version.
This way is possible to deploy a Java Gateway without the need to install
Zabbix Server components.
In the current state there wasn't an rcfile for the Java Gateway. [1]
PR: 217777
Reported by: Juan Garcia <juan@ish.com.au> [1]
Approved by: Pakhom Golynga <pg@pakhom.spb.ru> (maintainer)
net-mgmt/zabbix*: Fix fping location
Zabbix ports were patching fping location only in the config file,
so the default location of fping was wrong.
PR: 225956
Reported by: markham_breitbach@ssimicro.com
Approved by: Pakhom Golynga <pg@pakhom.spb.ru> (maintainer)
net-mgmt/zabbix24-*: Add note about the removal
Remove `-[0-9]*` from CONFLICTS
Reported by: mat
Approved by: garga (mentor), pg@pakhom.spb.ru (maintainer via email)
Differential Revision: https://reviews.freebsd.org/D10992
net-mgmt/zabbix2-server: rework LIB_DEPENDS and add USES= ssl
In my last commit i added accidently LIB_DEPENDS 2 additional times.
While here add USES= ssl and LIB_DEPENDS to port-mgmt/pkg to
pass QA.
Submitted by: Johannes Jost Meixner <johannes@perceivon.net>
net-mgmt/zabbix2-server: Update from 2.0.17 to 2.0.18
- updated French translation; thanks to Zabbix translators
- enforced bash usage in mysql.size user parameter configuration
script to avoid issues with different default shells;
thanks to Timo Lindfors for reporting it
- fixed timeout being too low when sending configuration data to
active proxy
- fixed loss of trailing whitespace in unquoted function parameters
when creating calculated items with low level discovery
Also:
- Fix default path to PID
- Fix rc.d scripts to correct use PID file
- Remove IGNORE_WITH_MYSQL because referenced version was removed long ago
PR: 209890
Submitted by: pg@pakhom.spb.ru (maintainer)
Approved by: pi (mentor)
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/openldap24-*:
- Convert to USES=libtool and bump dependent ports
- Avoid USE_AUTOTOOLS
- Don't use PTHREAD_LIBS
- Use MAKE_CMD
databases/glom:
- Drop :keepla
- Add INSTALL_TARGET=install-strip
databases/libgda4* databases/libgda5*:
- Convert to USES=libtool and bump dependent ports
- USES=tar:xz
- Use INSTALL_TARGET=install-strip
- Use @sample
(Only the first 15 lines of the commit message are shown above )
Fix unixODBC vs libiodbc conflicts
Always rely on unixODBC each time a port is looking for libodbc.so
Remove odbc compat from libiodbc
This allows to install both kde and gnome at the same time
While here:
- Convert libiodbc to USES=libtool
- Convert a bunch of libiodbc dependencies to USES=libtool
- Chase libiodbc.so shlib change
- Stagify some ports
- Convert some ports to USES=pgsql
Discussed with: rakuco (kde)
With hat: portmgr
- Update to 2.0.0 after repocopy from
net-mgmt/zabbix-{agent,frontend,proxy,server} [1]
- Convert to optionsNG
- Remove the need for SQL patches by using REINPLACE
- Remove manual installation of config files.
- Change config include directories from dirrm to dirrmtry in
pkg-plist - users may put files there.
PR: ports/169153 [1]
Submitted by: Pakhom Golynga <pakhom706@gmail.com> (maintainer)
Approved by: flo (mentor)
- Forced commit to note repocopy of :
net-mgmt/zabbix-server -> net-mgmt/zabbix2-server
net-mgmt/zabbix-agent -> net-mgmt/zabbix2-agent
net-mgmt/zabbit-frontend -> net-mgmt/zabbix2-frontend
net-mgmt/zabbix-proxy -> net-mgmt/zabbix2-proxy
- Note: This forced commit was performed as the repocopy took place prior
to the CVS->SVN migration and the requisite CVS post-repocopy forced
commit was not executed.
PR: ports/169153
Submitted by: Pakhom Golynga <pakhom706@gmail.com>
Repocopied by: marcus (portmgr)
Approved by: flo (mentor)
