[erlang-questions] "Can't set long node name" on Ubuntu using erl -name without suffix

Daniel Dormont dan@REDACTED
Fri Dec 9 20:08:26 CET 2011

A little more experimentation revealed that the problem was that the
system returned no FQDN for itself, as indicated for example by
'hostname -f'. A little /etc/hosts manipulation fixed that, and all
was well.


On Fri, Dec 9, 2011 at 12:56 PM, Daniel Dormont
<dan@REDACTED> wrote:
> On Fri, Dec 9, 2011 at 11:53 AM, Wes James <comptekki@REDACTED> wrote:
>> On Fri, Dec 9, 2011 at 9:39 AM, Daniel Dormont <dan@REDACTED> wrote:
>>> Hi everyone,
>>> I am just now starting to get into using long node names in my Erlang
>>> setup, running R14B02 on Ubuntu 11.10. Due to the way some of the
>>> internal scripts for Ejabberd are written, it would be convenient if I
>>> can start nodes using 'erl -name foo' without having to put anything
>>> after the @ sign. On some of my machines this works fine, but on
>>> others I get the error:
>> You will need to use -sname with that short name and the nodes will
>> only be available on the same subnet.
>> -name requires the full node@REDACTED
> Perhaps it's an unexpected or undocumented feature, but this is not
> true. For example, on one of my Amazon EC2 machines just now I ran
> 'erl -name foo' and got the following:
> Erlang R13B03 (erts-5.7.4) [source] [64-bit] [rq:1] [async-threads:0]
> [hipe] [kernel-poll:false]
> Eshell V5.7.4  (abort with ^G)
> (foo@REDACTED)1>
> no issues.
>> -wes

More information about the erlang-questions mailing list