<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Just to be clear, the remote VM dieing helps initiate the death of
the links or monitors, since the node is shown as down locally. You
can catch that condition separately with node monitoring.<br>
<br>
On 09/14/2012 06:55 PM, Michael Truog wrote:
<blockquote cite="mid:5053DFF8.6040700@gmail.com" type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
Yes, you will get a message from a monitor or link to a process on
a remote node, which requires that the nodes be connected, when
the remote process dies. You can just have premature death if the
net tick time is too long (not sure why, but it seemed like some
internal assumption that is made, not controlled by the net tick
time, saw in an older release but I assume it is the same still),
so that is why it is best to stick with the default net tick time,
unless you want to test that mechanism alot.<br>
<br>
On 09/14/2012 06:46 PM, Roberto Ostinelli wrote:
<blockquote
cite="mid:CAM5fRypo52mv86Qd+q0JMNK1tki56OxEhP-G5AUaW8n7CcZEqQ@mail.gmail.com"
type="cite"> hello Michael,
<div><br>
</div>
<div>you're assuming right (separate VM), I'm familiar with
links and monitors, thank you. However I doubt that any
message is sent from a dying process if the VM on which it
runs actually blows up. That was my point.</div>
<div><br>
</div>
<div>r.</div>
<div><br>
<br>
<div>On Fri, Sep 14, 2012 at 3:47 PM, Michael Truog <span><<a
moz-do-not-send="true" href="mailto:mjtruog@gmail.com">mjtruog@gmail.com</a>></span>
wrote:<br>
<blockquote>
<div> Assuming you have the 2 layers in separate Erlang
VMs. You can have the Erlang VMs connected with
distributed Erlang, and have the twin processes
monitoring each other. If you wanted a simple process
death if either died, you could consider using a link
instead of 2 monitors. However, that seems like the
simplest solution, to avoid unnecessary complexity. You
might find strangeness if you start not using the
default net tick time (i.e., with a process link
inbetween nodes), with distributed Erlang, but you
probably know it is best to not play with that.
<div>
<div><br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>