Advise to increase number of openfiles.

This commit is contained in:
ajacoutot 2010-10-02 16:16:10 +00:00
parent 4f2f939008
commit c5c1ac0e82
2 changed files with 17 additions and 4 deletions

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.29 2010/09/30 15:51:51 robert Exp $
# $OpenBSD: Makefile,v 1.30 2010/10/02 16:16:10 ajacoutot Exp $
COMMENT-main = network and application monitoring - agent
COMMENT-server = network and application monitoring - server
@ -13,7 +13,7 @@ FULLPKGNAME-web = zabbix-web-${VERSION}
FULLPKGPATH-web = net/zabbix,-web
CATEGORIES = net
REVISION-main= 2
REVISION-main= 3
MAJV = ${VERSION:C/^([0-9]+\.[0-9]+).*/\1/}

View File

@ -1,4 +1,4 @@
$OpenBSD: README.OpenBSD,v 1.7 2010/05/04 05:51:22 ajacoutot Exp $
$OpenBSD: README.OpenBSD,v 1.8 2010/10/02 16:16:10 ajacoutot Exp $
Using ZABBIX on OpenBSD
=======================
@ -34,7 +34,7 @@ Next, you have to adapt the configuration files under
addresses in the configuration files).
To have the ZABBIX server start at boot time, insert the following into
/etc/rc.local:
/etc/rc.local(8):
if [ -x ${TRUEPREFIX}/sbin/zabbix_server ]; then
install -d -o _zabbix /var/run/zabbix
@ -48,6 +48,19 @@ The Zabbix Server or Proxy might fail due to lack of shared memory
("Can't allocate shared memory..." errors), in which case you should set
kern.shminfo.shmall to 32768 -- see sysctl(8) and sysctl.conf(5).
On a busy server, it may be advisable to put the _zabbix user and
processes in their own login(1) class with tuned resources, such as more
open file descriptors etc.
e.g. add this to the login.conf(5) file:
zabbix:\
:openfiles-cur=1024:\
:openfiles-max=2048:\
:tc=daemon:
Then change the rc.local(8) zabbix_server start line with the following:
echo -n ' zabbix_server'; su -c zabbix root -c '/usr/local/sbin/zabbix_server'
The web frontend works reasonably well with OpenBSD's chroot'ed
httpd (the "Status of ZABBIX" page uses /bin/ps and /dev/kmem to
check the process, so it erroneously reports it as not running).