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

Ulf Wiger <>
Wed Apr 11 23:53:03 CEST 2012


On 11 Apr 2012, at 23:25, Ulf Wiger wrote:

> 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)
> ()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>}
> ()2> 
> 
> When starting erlang the normal way, I get the node name '', but when I start
> the net_kernel manually, I get ''.

Having experimented a bit, I found the following workaround:

Eshell V5.9  (abort with ^G)
1> inet_config:do_load_resolv(os:type(),longnames).
ok
2> net_kernel:start([n1,longnames]).
{ok,<0.34.0>}
()3> 

Comments?

BR,
Ulf W


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





More information about the erlang-bugs mailing list