Small blurb about shared memory.

This commit is contained in:
ajacoutot 2010-05-03 11:58:45 +00:00
parent 1a3b12a05b
commit ddc10f6bac
2 changed files with 7 additions and 3 deletions

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.21 2010/05/03 11:46:08 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.22 2010/05/03 11:58:45 ajacoutot Exp $
COMMENT-main = network and application monitoring - agent
COMMENT-server = network and application monitoring - server
@ -6,7 +6,7 @@ COMMENT-web = network and application monitoring - web frontend
VERSION = 1.8.2
DISTNAME = zabbix-${VERSION}
FULLPKGNAME-main = zabbix-agent-${VERSION}p1
FULLPKGNAME-main = zabbix-agent-${VERSION}p2
FULLPKGPATH-main = net/zabbix,-main
PKGNAME-server = zabbix-server-${VERSION}p0
FULLPKGNAME-web = zabbix-web-${VERSION}p1

View File

@ -1,4 +1,4 @@
$OpenBSD: README.OpenBSD,v 1.5 2010/05/03 11:46:08 ajacoutot Exp $
$OpenBSD: README.OpenBSD,v 1.6 2010/05/03 11:58:45 ajacoutot Exp $
This document gives information relevant to using ZABBIX on OpenBSD.
The original documentation is available as a PDF file at
@ -39,6 +39,10 @@ fi
For the proxy and the client, follow the same procedure, replacing
zabbix_server with zabbix_proxy or zabbix_clientd.
The Zabbix Server 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).
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).