From: Badlop <badlop@process-one.net>
Date: Tue, 6 Sep 2011 11:39:26 +0000 (+0200)
Subject: Clarification about system user of ejabberd.init
X-Git-Tag: v3.0.0-alpha-4~17
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b017702a15c0836d4ad6b42020b96e2f6845b423;p=ejabberd

Clarification about system user of ejabberd.init
---

diff --git a/doc/guide.tex b/doc/guide.tex
index 0c9483c2b..28be76c66 100644
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -251,8 +251,9 @@ and for example it doesn't read the file ejabberdctl.cfg.
 On a *nix system, if you want ejabberd to be started as daemon at boot time,
 copy \term{ejabberd.init} from the 'bin' directory to something like \term{/etc/init.d/ejabberd}
 (depending on your distribution).
-Create a system user called \term{ejabberd};
-it will be used by the script to start the server.
+Create a system user called \term{ejabberd},
+give it write access to the directories \term{database/} and \term{logs/}, and set that as home;
+the script will start the server with that user.
 Then you can call \term{/etc/inid.d/ejabberd start} as root to start the server.
 
 If \term{ejabberd} doesn't start correctly in Windows,