- add a small warning in MESSAGE and tweak the starting command ;

if gnugk is ran as an unpriviledged user, the current directory has to
be accessible by it
This commit is contained in:
ajacoutot 2007-08-30 15:14:16 +00:00
parent ee36d3dde2
commit 45bb34e8a9
2 changed files with 5 additions and 4 deletions

View File

@ -1,11 +1,11 @@
# $OpenBSD: Makefile,v 1.3 2007/08/02 14:39:36 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.4 2007/08/30 15:14:16 ajacoutot Exp $
SHARED_ONLY= Yes
COMMENT= H.323 gatekeeper
DISTNAME= gnugk-2.2.6
PKGNAME= ${DISTNAME}p0
PKGNAME= ${DISTNAME}p1
CATEGORIES= net telephony
HOMEPAGE= http://www.gnugk.org/

View File

@ -1,5 +1,6 @@
To start the gatekeeper as the unpriviledged ${GNUGK_ID} user, as root:
(Warning: make sure ${GNUGK_ID} has access to the current directory)
install -d -o _gnugk /var/run/gnugk
${PREFIX}/bin/gnugk -c /etc/gnugk.ini -u _gnugk \
-o /var/log/gnugk/gnugk.log --pid /var/run/gnugk/gnugk.pid >/dev/null &
${PREFIX}/bin/gnugk -t -c /etc/gnugk.ini -u _gnugk \
-o /var/log/gnugk/gnugk.log --pid /var/run/gnugk/gnugk.pid 1> /dev/null &