Starting processes at remote nodes

Martin Bjorklund <>
Mon Jun 7 09:39:40 CEST 2004


Vance Shipley <> wrote:
> Folks,
> 
> Is there a good reason why we don't have a proc_lib function
> to synchronously start a process on a remote node?

proc_lib and gen_* _could_ have these functions, but a supervisor
should only supervise local processes, otherwise it can't do it's job
properly - which is to guarantee that workers are running according to
the specs, and exit if they don't.

Suppose that supervisor S runs on A and supervises W on node B.  now
the link between A and B goes down.  S will get a
{'EXIT',W,noconnection} message.  Now what should S do?

The other problem is that the supervision tree is used to find
processes during code upgrade.  If the module for W is upgraded on
node B, W will not be found.



/martin



More information about the erlang-questions mailing list