25
1
mirror of https://github.com/processone/ejabberd.git synced 2024-11-28 16:34:13 +01:00

Clarification about system user of ejabberd.init

This commit is contained in:
Badlop 2011-09-06 13:39:26 +02:00
parent 20f3fc96c3
commit 3eca0259f7

View File

@ -250,8 +250,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, 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} copy \term{ejabberd.init} from the 'bin' directory to something like \term{/etc/init.d/ejabberd}
(depending on your distribution). (depending on your distribution).
Create a system user called \term{ejabberd}; Create a system user called \term{ejabberd},
it will be used by the script to start the server. 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. 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, If \term{ejabberd} doesn't start correctly in Windows,