From 342ea2753c18bec49466ba5204505e8d4bb1a237 Mon Sep 17 00:00:00 2001
From: Badlop <badlop@process-one.net>
Date: Mon, 24 Aug 2009 19:44:21 +0000
Subject: Document that the admin can install ejabberd.init script (EJAB-755)

SVN Revision: 2522
---
 doc/guide.tex | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

(limited to 'doc/guide.tex')

diff --git a/doc/guide.tex b/doc/guide.tex
index 0318d8939..924ad2478 100644
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -242,7 +242,10 @@ 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) and call \term{/etc/inid.d/ejabberd start} to start it.
+(depending on your distribution).
+Create a system user called \term{ejabberd};
+it will be used by the script to start the server.
+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,
 try to start it using the shortcut in desktop or start menu.
@@ -449,6 +452,13 @@ and can identify what is exactly the problem.
 Please refer to the section~\ref{ejabberdctl} for details about \term{ejabberdctl},
 and configurable options to fine tune the Erlang runtime system.
 
+If you want ejabberd to be started as daemon at boot time,
+copy \term{ejabberd.init} 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.
+Then you can call \term{/etc/inid.d/ejabberd start} as root to start the server.
+
 \makesubsection{bsd}{Specific Notes for BSD}
 \ind{install!bsd}
 
-- 
cgit v1.2.3

