aboutsummaryrefslogtreecommitdiffstats
path: root/lib/kernel/src/pg2.erl
diff options
context:
space:
mode:
authorMagnus Henoch <[email protected]>2013-01-25 16:54:12 +0000
committerMagnus Henoch <[email protected]>2013-01-25 16:54:12 +0000
commit0e328bd14f2bc0e05cfc1ce6c44f3692af58ea03 (patch)
tree582701e2776f1c05245aae7951331ab139b84720 /lib/kernel/src/pg2.erl
parent907d498ff798345fc8e8b71fc08a1c5b40112037 (diff)
downloadotp-0e328bd14f2bc0e05cfc1ce6c44f3692af58ea03.tar.gz
otp-0e328bd14f2bc0e05cfc1ce6c44f3692af58ea03.tar.bz2
otp-0e328bd14f2bc0e05cfc1ce6c44f3692af58ea03.zip
Slightly nicer error message when node start fails due to duplicate name
When starting up an Erlang node using a node name that is already in use, the new node used to crash with output starting with this message: {error_logger,{{2013,1,25},{16,0,42}},"Protocol: ~p: register error: ~p~n",["inet_tcp",{{badmatch,{error,duplicate_name}},[{inet_tcp_dist,listen,1,[..... With this change, the first line in the output changes to: {error_logger,{{2013,1,25},{16,40,41}},"Protocol: ~tp: the name foo@localhost seems to be in use by another Erlang node",["inet_tcp"]}
Diffstat (limited to 'lib/kernel/src/pg2.erl')
0 files changed, 0 insertions, 0 deletions