* doc/Makefile: Remove bashism

* doc/guide.tex: Document how to change computer
hostname (EJAB-320)

SVN Revision: 1034

diff --git a/ChangeLog b/ChangeLog
index 3ace69525192edb7bc2bf50c9953756b37951cf4..f55968581c6416bee1605d35006aeb42b4a85e08 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,10 @@
 2007-12-06  Badlop  <badlop@process-one.net>
 
+       * doc/Makefile: Remove bashism
+
+       * doc/guide.tex: Document how to change computer
+       hostname (EJAB-320)
+
        * src/web/ejabberd_http.erl: Change loglevel for http
        queries (EJAB-363)
        * src/web/ejabberd_web_admin.erl: Likewise

diff --git a/doc/guide.tex b/doc/guide.tex
index 1ce9f332542bc5eeb696e3f1cfcb0aefed6f0766..5237ef9fdb47299c54bcde357a69c290ac74fbd1 100644 (file)
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -3386,6 +3386,33 @@ and you must login in the Jabber server with
 an account with proper privileges.
 
 
+\section{Change Computer Hostname}
+\label{changeerlangnodename}
+
+ejabberd uses the distributed Mnesia database. 
+Being distributed, Mnesia enforces consistency of its file,
+so it stores the name of the Erlang node in it.
+The name of an Erlang node includes the hostname of the computer.
+So, the name of the Erlang node changes
+if you change the name of the machine in which ejabberd runs,
+or when you move ejabberd to a different machine.
+
+So, if you want to change the computer hostname where ejabberd is installed,
+you must follow these instructions:
+\begin{enumerate}
+       \item In the old server, backup the Mnesia database using the Web Interface or \term{ejabberdctl}.
+       For example: 
+\begin{verbatim}
+ejabberdctl backup /tmp/ejabberd-oldhost.backup
+\end{verbatim}
+       \item In the new server, restore the backup file using the Web Interface or \term{ejabberdctl}.
+       For example:
+\begin{verbatim}
+ejabberdctl restore /tmp/ejabberd-oldhost.backup
+\end{verbatim}
+\end{enumerate}
+
+
 \chapter{Securing ejabberd}
 \section{Firewall Settings}
 \label{firewall}