* doc/Makefile: Remove bashism

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

SVN Revision: 1034

2 files changed, 32 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index 3ace6952..f5596858 100644
--- 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 1ce9f332..5237ef9f 100644
--- 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}