Questions about "erl -epmd_start false"

[Jérôme de Bretagne]

Hi Shino,

This behavior is indeed expected.

To avoir all registrations to epmd, you can pass the -no_epmd option
instead.

It is mentioned in the following documentation:
https://erlang.org/doc/apps/erts/alt_dist.html

Cheers,
Jérôme

Le ven. 18 déc. 2020 à 03:40, Shunichi Shinohara <shino.shun@REDACTED> a
écrit :

> Hi List,
>
> I try "epmdlessless" configuration described in:
>   Running Erlang Releases without EPMD on OTP 23.1+ · Erlware Blog
>   https://blog.erlware.org/epmdlessless/
>
> It works as described, thanks to people who contributed to the feature!
> However, it behaves in an unexpected way (to me) under epmd daemon running
> case.
>
> Expected behavior is the case without running epmd daemon. After launching
> a node as:
>
> % erl -sname foo -start_epmd false -erl_epmd_port 14693
> Erlang/OTP 23 [erts-11.1.4] [source] [64-bit] [smp:16:16] [ds:16:16:10]
> [async-threads:1]
>
> epmd daemon does *NOT* start, as expected:
>
> % epmd -names
> epmd: Cannot connect to local epmd
>
> On the other hand, after epmd daemon started as epmd -daemon,
> by executing the same erl command above, the node is registered to epmd
> daemon:
>
> % epmd -names
> epmd: up and running on port 4369 with data:
> name foo at port 14693
>
> The questions are:
> - Is this behavior expected (to other than me)?
> - Is there any option(s) of erl command to avoid registration to epmd?
>   # I guess it's possible by using https://github.com/tsloughter/epmdless
>
> Thanks,
> Shino
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20201218/7d5a108c/attachment.htm>