Ejabberd runtime configuration: Unterschied zwischen den Versionen

Aus Free Software
Zur Navigation springen Zur Suche springen
K (Reverted edits by Ijicusyd (talk) to last revision by Mati)
Zeile 12: Zeile 12:
* Some of the tricks are from [http://www.ejabberd.im/tricks here]
* Some of the tricks are from [http://www.ejabberd.im/tricks here]
* [http://www.ejabberd.im/interconnect-erl-nodes Interconnecting Erlang nodes]
* [http://www.ejabberd.im/interconnect-erl-nodes Interconnecting Erlang nodes]
* [http://jsmart.web.id/Ejabberd jsmart.web.id]

Version vom 30. Juni 2013, 17:39 Uhr

You can change lots of the configuration at runtime either via the webinterface or by attaching to the ejabberd node. You can do the latter by running "ejabberdctl debug", where you can run any of the following commands:

Check Syntax of file
file:consult("/etc/ejabberd/ejabberd.cfg").
Reload config-file
ejabberd_config:load_file("/etc/ejabberd/ejabberd.cfg").
Note that this only updates ACL and Shapers. Listening ports, virtual hosts, modules and all major options will not change.
Add codepath
code:add_patha("/usr/lib/erlang/lib/xmlrpc-1.13/").
Set loglevel
ejabberd_loglevel:set(4).

Note: A loglevel of 5 sometimes causes additional debug messages on stdout (which breaks munin plugins).
Get loglevel
ejabberd_loglevel:get().
Reload module
l(mod_version).
Where mod_version is the module you want to reload.
Recompile module
c(mod_version).
Where mod_version is the module you want to compile. You will still have to reload the module.

See also