Chapril/xmpp.chapril.org-ejabberd
25
1
Fork 0
mirror of https://github.com/processone/ejabberd.git synced 2024-11-22 16:20:52 +01:00
Code Releases Activity

* doc/Makefile: Remove bashism

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

SVN Revision: 1034
This commit is contained in:
Badlop 2007-12-06 15:26:53 +00:00
parent 4f78230dd8
commit 386f432977
2 changed files with 32 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -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

27
doc/guide.tex
View File

@ -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}