erl -name XXX problem

[Peter-Henry Mander]

Hi Joe,

May I also add (because I had the same problem) that the 
$HOME/.erlang.cookie file in your home directory needs to be copied to 
the machines you wish to communicate with in order to authenicate the 
commincating nodes. I have read in one mailing that you can achieve the 
same result with erl -cookie <cookie_string>, but it is less secure.

c.f. http://www.erlang.org/ml-archive/erlang-questions/200108/msg00016.html
and http://www.erlang.org/doc/r8b/lib/kernel-2.7.3/doc/html/auth.html 
(which erroneously refers to $HOME/erlang.cookie without a dot prefix)

The default behavior is to create an arbitrarily random .erlang.cookie 
file, which will prevent nodes from authorising communication.

Pete.

Luke Gorrie wrote:

>Joe Armstrong <joe@REDACTED> writes:
>
>  
>
>>   If I do erl -name joe
>>
>>   My system bails out with a horrendous error message - the start of which is
>>
>>{error_logger,{{2002,10,25},{12,6,18}},
>>	'Can\'t set long node name!\nPlease check your configuration\n',[]}
>>
>>   What do I have to do to fix this??
>>    
>>
>
>Sure I should be waiting for the experts, but :-)
>
>If you run "domainname" in the shell, does it print your domain? If
>not, you can do e.g. "domainname bluetail.com" (as root) to set it.
>
>If that diagnosis was right, I think the persistent fix is to put a
>line like "domain bluetail.com" at the top of /etc/resolv.conf
>
>(NB: 'erl -name joe' works on R9B on my machine)
>
>Cheers,
>Luke
>
>
>
>  
>