If you want ejabberd to run

teo — Sat, 07 Jan 2006 07:44:49 +0000

If you want ejabberd to run not on the distributed node you could omit -name or -sname command line option. In this case epmd woold't be run and beam would't listen network.

But you'd loose the options of controlling ejabberd via ejabberdctl. Moreover, ejabberd web-interface uses distributed erlang features for example for modules management etc.

The worst thing you'd get is that it'd be impossible to stop ejabberd cleanly. The only way would be to kill beam, which can result in database corruption.

I don't know if epmd can be

mfoss — Thu, 05 Jan 2006 12:02:11 +0000

I don't know if epmd can be 'disabled'.

If you can't shutdown epmd, you can simply discard connections to port 4369 on your firewall. The other listening port is not always 39309, I think it varies upon restart.

ejabberd - Comments for "IP-Adress and port of epmd"

If you want ejabberd to run

I don't know if epmd can be