ansaurus

Question

Stop Erlang Daemon

Answer 1

+7 A:

kill and killall with -9 is almost always wrong.

You can quite easily ask the remote node to exit using:

rpc:call(RemoteNode, init, stop, []).

I don't know whether that'd prevent heart from restarting it, but I'd suggest that if you expect to stop it, you shouldn't run it in a don't-ever-stop mode.

Update - Zed points out that init:stop does the right thing with heart, so the above rpc:call is the best and only way to do it.

Dustin 2010-01-25 07:15:11

"init:stop(): ... If the -heart command line flag was given, the heart program is terminated before the Erlang node terminates. ..."

Zed 2010-01-25 07:41:36

I think my nodes aren't quite connecting. I'm sure I'm overlooking something. To test, I opened two Terminal windows and ran `erl -sname foo` in one, then got the cookie from it and ran `erl -sname bar -setcookie '...'`. In this window, I ran `net_adm:ping('foo@elife')` but it gave me a 'pang'. I've tried some variants on this, all without luck. Any idea what I'm doing wrong?

Eli 2010-01-25 16:07:02

Why are you doing `-setcookie` on one and not the other? If they don't match, you can't talk. In generally, I just use `~/.erlang.cookie` on my local node.

Dustin 2010-01-25 18:14:52

I set them both to use the same cookie, but still, no communication. Any ideas?

Eli 2010-01-26 00:54:21

Could be a number of things. You should definitely have that working, though. That's another question or more documentation, though. You could try `-name [email protected]` which should probably work.

Dustin 2010-01-26 04:57:40

Are you running OS X? If so, this might be your problem as well: http://stackoverflow.com/questions/2136918/getting-two-erl-shells-to-talk

Adam Lindberg 2010-01-28 19:59:09

ansaurus

tags:

views:

answers:

Stop Erlang Daemon

related questions