diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/guide.html | 15 | ||||
| -rw-r--r-- | doc/guide.tex | 15 |
2 files changed, 28 insertions, 2 deletions
diff --git a/doc/guide.html b/doc/guide.html index af65e7ea..4ecd8242 100644 --- a/doc/guide.html +++ b/doc/guide.html @@ -290,7 +290,13 @@ 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>The <TT>ejabberdctl</TT> administration script is included in the <TT>bin</TT> directory. +(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 and a crash dump is generated, +there was a severe problem. +You can try starting <TT>ejabberd</TT> with +the script <TT>bin/live.bat</TT> in Windows, +or with the command <TT>bin/ejabberdctl live</TT> in other Operating Systems. +This way you see the error message provided by Erlang +and can identify what is exactly the problem.</P><P>The <TT>ejabberdctl</TT> administration script is included in the <TT>bin</TT> directory. 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="install.os"></A> </P><!--TOC section Installing <TT>ejabberd</TT> with Operating System specific packages--> <H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6">2.2</A>  <A HREF="#install.os">Installing <TT>ejabberd</TT> with Operating System specific packages</A></H2><!--SEC END --><P> <A NAME="install.os"></A> </P><P>Some Operating Systems provide a specific <TT>ejabberd</TT> package adapted to @@ -405,7 +411,12 @@ Node ejabberd@localhost is started. Status: started ejabberd is running ejabberdctl stop -</PRE><P>Please refer to the section <A HREF="#ejabberdctl">4.1</A> for details about <TT>ejabberdctl</TT>, +</PRE><P>If <TT>ejabberd</TT> doesn’t start correctly and a crash dump is generated, +there was a severe problem. +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--> <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: diff --git a/doc/guide.tex b/doc/guide.tex index bf07f39e..f01dd9be 100644 --- a/doc/guide.tex +++ b/doc/guide.tex @@ -241,6 +241,14 @@ 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. +If \term{ejabberd} doesn't start correctly and a crash dump is generated, +there was a severe problem. +You can try starting \term{ejabberd} with +the script \term{bin/live.bat} in Windows, +or with the command \term{bin/ejabberdctl live} in other Operating Systems. +This way you see the error message provided by Erlang +and can identify what is exactly the problem. + The \term{ejabberdctl} administration script is included in the \term{bin} directory. Please refer to the section~\ref{ejabberdctl} for details about \term{ejabberdctl}, and configurable options to fine tune the Erlang runtime system. @@ -415,6 +423,13 @@ ejabberd is running ejabberdctl stop \end{verbatim} +If \term{ejabberd} doesn't start correctly and a crash dump is generated, +there was a severe problem. +You can try starting \term{ejabberd} with +the command \term{ejabberdctl live} +to see the error message provided by Erlang +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. |