[erlang-questions] starting with long name fails
Thu Jun 14 08:26:10 CEST 2012
Thanks Daniel, I had missed that thread.
As it happens, I have some machines that aren't configured properly
and I didn't see that as long as I was only connecting several nodes
on the same machine. When I got really distributed, then the problem
became apparent. I hope I can get the admin to fix the
> On Wed, Jun 13, 2012 at 6:09 PM, Daniel Dormont <dan@REDACTED>
>> I had a similar question a few months ago. Here was the response.
>> Short answer, 'erl -name foo' without an @ sign (or anything after it) is
>> indeed the preferred way to start a long-named node, but it only works if
>> the machine has a FQDN (note that this can be faked using a host file if
>> your DNS isn't set up to give you one).
>> On Wed, Jun 13, 2012 at 5:10 PM, Vlad Dumitrescu <vladdu55@REDACTED>
>>> I am a little confused, hopefully someone can get me on the right track.
>>> I noticed that on some machines, when starting "erl -name foo", I get
>>> an error "Can't set long name!". I suppose this is because the machine
>>> doesn't have a properly configured FQDN?
>>> Also, I don't know where I had gotten this idea from, but I was using
>>> "erl -name foo@REDACTED". This works fine with any weird value for the
>>> host name, but of course there will be problem if the real host name
>>> isn't "mypc.com". Given that sometimes (as above) the runtime checks
>>> for a valid host name, why does it allow anything if specified on the
>>> comman line? (Needless to saay, I got in some delicate situation
>>> because of this :-)
>>> best regards,
>>> erlang-questions mailing list
> erlang-questions mailing list
More information about the erlang-questions