diff options
Diffstat (limited to '')
| -rw-r--r-- | doc/guide.html | 12 | ||||
| -rw-r--r-- | doc/guide.tex | 12 |
2 files changed, 21 insertions, 3 deletions
diff --git a/doc/guide.html b/doc/guide.html index 29eb80f2..350964fa 100644 --- a/doc/guide.html +++ b/doc/guide.html @@ -300,7 +300,10 @@ go to the Windows service settings and set ejabberd to be automatically started. Note that the Windows service is a feature still in development, and for example it doesn’t read the file ejabberdctl.cfg.</P><P>On a *nix system, if you want ejabberd to be started as daemon at boot time, copy <TT>ejabberd.init</TT> from the ’bin’ directory to something like <TT>/etc/init.d/ejabberd</TT> -(depending on your distribution) and call <TT>/etc/inid.d/ejabberd start</TT> to start it.</P><P>If <TT>ejabberd</TT> doesn’t start correctly in Windows, +(depending on your distribution). +Create a system user called <TT>ejabberd</TT>; +it will be used by the script to start the server. +Then you can call <TT>/etc/inid.d/ejabberd start</TT> as root to start the server.</P><P>If <TT>ejabberd</TT> doesn’t start correctly in Windows, try to start it using the shortcut in desktop or start menu. If the window shows error 14001, the solution is to install: "Microsoft Visual C++ 2005 SP1 Redistributable Package". @@ -438,7 +441,12 @@ You can try starting <TT>ejabberd</TT> with the command <TT>ejabberdctl live</TT> to see the error message provided by Erlang and can identify what is exactly the problem.</P><P>Please refer to the section <A HREF="#ejabberdctl">4.1</A> for details about <TT>ejabberdctl</TT>, -and configurable options to fine tune the Erlang runtime system.</P><P> <A NAME="bsd"></A> </P><!--TOC subsection Specific Notes for BSD--> +and configurable options to fine tune the Erlang runtime system.</P><P>If you want ejabberd to be started as daemon at boot time, +copy <TT>ejabberd.init</TT> to something like <TT>/etc/init.d/ejabberd</TT> +(depending on your distribution). +Create a system user called <TT>ejabberd</TT>; +it will be used by the script to start the server. +Then you can call <TT>/etc/inid.d/ejabberd start</TT> as root to start the server.</P><P> <A NAME="bsd"></A> </P><!--TOC subsection Specific Notes for BSD--> <H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc14">2.4.6</A>  <A HREF="#bsd">Specific Notes for BSD</A></H3><!--SEC END --><P> <A NAME="bsd"></A> </P><P>The command to compile <TT>ejabberd</TT> in BSD systems is: </P><PRE CLASS="verbatim">gmake diff --git a/doc/guide.tex b/doc/guide.tex index 0318d893..924ad247 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} |