[erlang-bugs] net_kernel:start/1 going its own way

[Ulf Wiger]

I just noticed this confusing behavior:

uwair: uwiger$ erl -name n1
Erlang R15B (erts-5.9) [source] [64-bit] [smp:4:4] [async-threads:0] [hipe] [kernel-poll:false]

Eshell V5.9  (abort with ^G)
(n1@REDACTED)1> 
BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded
       (v)ersion (k)ill (D)b-tables (d)istribution
a
uwair: uwiger$ erl
Erlang R15B (erts-5.9) [source] [64-bit] [smp:4:4] [async-threads:0] [hipe] [kernel-poll:false]

Eshell V5.9  (abort with ^G)
1> net_kernel:start([n1, longnames]).
{ok,<0.33.0>}
(n1@REDACTED)2> 

When starting erlang the normal way, I get the node name 'n1@REDACTED', but when I start
the net_kernel manually, I get 'n1@REDACTED'.

I have yet to delve into the code to figure out where the two approaches part ways, but an
obvious problem is that rebar's node tool uses the second approach, which on my machine
causes nodetool to fail when trying to ping the newly started node.

Most likely, something is not quite right in my environment, but why should this matter in the first place?

BR,
Ulf W

Ulf Wiger, Co-founder & Developer Advocate, Feuerlabs Inc.
http://feuerlabs.com