weekend erlang programmer


{2010, 4, 8}

net_kernel:start/1問題まとめ - erlang-questionsにメール送ってみた 01:18 はてなブックマーク - net_kernel:start/1問題まとめ - erlang-questionsにメール送ってみた - weekend erlang programmer net_kernel:start/1問題まとめ - erlang-questionsにメール送ってみた - weekend erlang programmer のブックマークコメント


how to configure node with net_kernel:start/1

I'm writing a self-configuring node cluster with net_kernel:start/1.

It starts without -name nor -sname option and gets its IP adress from inet:getif/0.

And they configure themselves with net_kernel:start/1 as follows:

net_kernel:start( [ 'appname@', longnames ] ).

Servers find each other by sending its longname by UDP broadcasting, and they connects each other.

The problem is, starting erl without -name option it doesn't kick epmd and following net_kernel:start/1 fails in tcp_inet_dist:listen (maybe because of epmd not running).

And another way - starting with -name option with bad ip address ( or local ip) makes net_kernel:start/1 result in {error, not_allowed}.

Is it a wrong to think that if epmd would start when net_kernel:start/1 had been called, isn't it?