EJABBERD MNESIA TABLES MANUAL

Resources, and that is why the behaviour it implements is not the default. Usage of the -concurrent option creates additional pressure on the server Site), you can pass the -concurrent option to ejabberdctl which will ensure no If, conversely, there is a chance for several instances of ejabberdctl to be activeĪt the same time (say, automated registration of new users on an actively used When ejabberdctl is only run manually from time to time by a server administrator Instances of it in parallel–the second one will fail. user and host are the respective parts of the entity JID and password isĮither a plain text password to authenticate that JID or the MD5 hash of thatĭue to the way ejabberdctl is implemented, it is normally not possible to run two This option must be used to authenticate the entity requesting execution of theĬommand. If restriction of access to ejabberdctl commands is configured (see the 'RestrictĮxecution with AccessCommands' section in the Installation and Operation Guide),

EJABBERD MNESIA TABLES MANUAL

If the node nameĬontains a symbol and its hostname part is a FQDN then ejabberd will use so-Ĭalled long names (see erl(1) manual page and look for options -name and -sname forĮjabberd Connect to locally run ejabberd server at node Connect to remotely run ejabberd server at Connect to locally run ejabberd server at honors ERLANG_NODE environment variable from /etc/default/ejabberd, see Host is short hostname (usually it coincides with `hostname -s`). Name does not contain a symbol then the actual node name becomes where Specifies remote Erlang node to connect to. This command must be run either by a superuser or by the user ejabberd, otherwise it willįail to start or to connect to the ejabberd instance.

The administrator control the functioning of the running ejabberd daemon.

SYNOPSIS ejabberdctl ] DESCRIPTION ejabberdctl is a front end to the ejabberd Jabber/XMPP server. Ejabberdctl - a control interface of ejabberd Jabber/XMPP server

Ejabberd mnesia tables