slaves and remote nodes... How do you start them?

[Serge Aleynikov]

slave:start/3 accepts Args as the third parameter where you could pass 
the startup arguments:

Args = "-pa /path/to/the/boot/dir -boot bootfilename",
slave:start(host1, node_name, Args).

This will indeed start a slave node using the bootfilename.

OTOH, perhaps you could start the nodes independently, and implement 
some synchronization protocol based on message passing, or pg2.

Regards,

Serge

Rudolph van Graan wrote:
> Suppose I have file system with lots of interdependent erlang applications.
> I need a couple of nodes that make up my system.
> So each type of node has a different boot script.
> I would like to have an ordered way of starting the system. For example:
> 
> 1. Start the mnesia node(s)
> 2. Start the application server(s)
> 3. Start the web server(s)
> 
> I would like to start all these from a single erlang VM as slave nodes. 
> (So that I don't have to try and get them to start correctly from 
> outside erlang in scripts).
> 
> Looking at the documentation for slave:
> 
> start(Host)
> start_link(Host, Name)
> start(Host, Name, Args) -> {ok, Node} | {error, ErrorInfo}
> etc
> 
> None of these functions give me a way to start each node by specifying 
> the boot script for the node type.
> 
> How do other people do this? Or am I going to have to start this system 
> the hard way?
> 
> Rudolph van Graan
> 
> Telecommunications Specialist
> Pattern Matched Technologies
> 
> E-Mail:  rvg@REDACTED
> Mobile:  +27 83 390 7767
> Fax:     +27 12 667 5342
> Web:     www.patternmatched.com
> 
> 
>