I have just been looking at the slave (nodes) module.
>From what I can see it says that (currently) nodes running on an NT
machine cannot spawn slave nodes onto another host.
Can anyone confirm if this is still the case?
Also, I was wondering what the pattern was for storing node/host
configuration data within an Erlang application? I currently pass all my
configuration data in via the associated .app file.
This of course gets messy quickly - is there another way of doing it
that I may be missing perhaps?
Many Thanks,
Dan
I think on Windows you can only spawn local slaves (or can't spawn at all).
I modified the source code to use psexec.exe instead of ssh, but if you want
a clean solution, I think you need to write a little .bat/.cmd script, which
spawning erl.exe on another node and specify it using -rsh option, when you
launching you master node.
Zvi
> _______________________________________________
> erlang-questions mailing list
> erlang-q...@erlang.org
> http://www.erlang.org/mailman/listinfo/erlang-questions
>
>
--
View this message in context: http://www.nabble.com/Slave-nodes...-tp20524567p20524925.html
Sent from the Erlang Questions mailing list archive at Nabble.com.
Do you mean something similar to that suggested in:
http://www.berabera.info/oldblog/lenglet/howtos/erlangkerberosremctl/index.html
I would certainly be interested in hearing from someone who has
experience deploying an erlang app across a number of nodes - I would
like to know the best way of storing the node configuration i.e.
describing which nodes are going to be used for particular conponents.
Thanks,
Dan