[erlang-patches] jinterface: OtpEpmd.get
Thu Sep 20 12:09:05 CEST 2012
Thanks for the hint. I'll try that. The only relevant tests are from users
that have this configuration problem but it feels safe enough.
On Thu, Sep 20, 2012 at 11:58 AM, Henrik Nord <> wrote:
> (Raimo wrote)
> Could you try: + return lookupNames(InetAddress.**getByName(null));
> instead, as it is documented to return the loopback address. That would
> save us from surprises if "localhost" is strangely configured. The epmd
> will listen to * so locally using the loopback address should always work.
> If we one day change socket type (configurable) in OtpEpmd to inet6 I guess
> the corresponding ::1 address is returned by the above line.
> Thank you for your contributions!
> On 09/19/2012 11:19 AM, Vlad Dumitrescu wrote:
>> I found a problem with OtpEpmd if the network is badly configured:
>> In an enterprise environment, it's not an easy task to get the machine
>> configuration corrected.
>> On some machines with weird network configurations,
>> InetAddress.getLocalHost() hangs. Searching for "localhost" works (at
>> least in the cases I met). The difference is that the loopback address
>> will be returned, instead of the real IP address, but for the local
>> machine this should not be a problem.
>> git fetch git://github.com/vladdu/otp.**git<http://github.com/vladdu/otp.git>jinterface_epmd_localhost
>> I don't know how to configure the network to provoke the problem, but
>> I just got confirmation from someone that has it that with this fix
>> everything works as expected.
>> [Note that for this user, "erl -sname foo" and "erl -sname bar" can't
>> connect to each other, one has to use "erl -sname "]
>> There are no tests covering OtpEpmd, would this change require any?
>> best regards,
>> erlang-patches mailing list
> /Henrik Nord Erlang/OTP
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-patches