epmd

Starting the erlang VM without epmd

谁说我不能喝 提交于 2019-12-07 13:11:26
问题 I'm trying to startup epmd separately from the erlang vm, in order to do monitoring on the connection handling. This works fine, except for cases when the vm starts up before epmd. Is there a way to make the erlang vm start without it starting the epmd on its own? 回答1: Possible helpful questions/answers: Is there a way to stop Erlang servers from automatically starting epmd? Ensure epmd started So inline with those questions/answers, I'd suggest to make the erlang vm service depend on epmd

Starting the erlang VM without epmd

假如想象 提交于 2019-12-05 20:18:36
I'm trying to startup epmd separately from the erlang vm, in order to do monitoring on the connection handling. This works fine, except for cases when the vm starts up before epmd. Is there a way to make the erlang vm start without it starting the epmd on its own? marcelog Possible helpful questions/answers: Is there a way to stop Erlang servers from automatically starting epmd? Ensure epmd started So inline with those questions/answers, I'd suggest to make the erlang vm service depend on epmd (which should be another service on its own). Also, if you run epmd as one of your very first

Is there a way to stop Erlang servers from automatically starting epmd?

生来就可爱ヽ(ⅴ<●) 提交于 2019-11-28 12:23:16
Erlang servers will automatically spawn epmd (the Erlang port mapper daemon) if it isn't already running. I would prefer to manage epmd using systemd as a separate service. This is so that if I have multiple Erlang servers running on one host (e.g. RabbitMQ and ejabberd), epmd won't dissapear if the server that automatically spawned epmd gets shut down. systemd will clean up any stray processes when a service gets shut down so an automatically spawned epmd won't survive. I can mostly handle this by making sure epmd is running as a separate service before starting any Erlang servers but I want

Is there a way to stop Erlang servers from automatically starting epmd?

限于喜欢 提交于 2019-11-27 07:06:16
问题 Erlang servers will automatically spawn epmd (the Erlang port mapper daemon) if it isn't already running. I would prefer to manage epmd using systemd as a separate service. This is so that if I have multiple Erlang servers running on one host (e.g. RabbitMQ and ejabberd), epmd won't dissapear if the server that automatically spawned epmd gets shut down. systemd will clean up any stray processes when a service gets shut down so an automatically spawned epmd won't survive. I can mostly handle