[erlang-questions] erlang gen_tcp:connect/3 not working with rpc:call/4, anyone knows why?

Magnus Klaar magnus.klaar@REDACTED
Wed Sep 21 20:18:51 CEST 2011


The Erlang VM provides multiple strategies for name lookups, among them is a
native lookup mechamism using getaddrinfo and
an erlang client implemented by the inet_res module.

The contents of the inet_db table on the detached node may also be worth
looking into, does it differ? which strategy does it use?. You can access it

rpc:call('loadtest@REDACTED', ets,tab2list,[inet_db]).

You may also want to look into the mDNSResponder daemon that OSX uses as a
system-wide resolver. this daemon appears to
be an alternative to the nscd deamon found on GNU/Linux systems.
Applications are expected to perform lookups against this daemon.

MVH Magnus

On Wed, Sep 21, 2011 at 7:03 PM, Allen Kim <allen.kim@REDACTED>wrote:

> It IS Mac OS X issue, definitely.
> I ran it from CentOS box, and it works fine.
> Don't know why it does not work on Mac OS X though.
> On 11-09-21 12:35 PM, "Allen Kim" <allen.kim@REDACTED> wrote:
> >$cat /etc/resolv.conf
> >#
> ># Mac OS X Notice
> >#
> ># This file is not used by the host name and address resolution
> ># or the DNS query routing mechanisms used by most processes on
> ># this Mac OS X system.
> >#
> ># This file is automatically generated.
> >#
> >nameserver
> >
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110921/ee3971f8/attachment.htm>

More information about the erlang-questions mailing list