Starting a slave node in particular directory

[Slobodan Miskovic]

Hi all,

I am writing a cluster master portion of my system but am having issues with the current working directory on slave nodes.
For certain applications (in particular yaws:start_embedded) the files:set_cwd doesn't seem to affect directory in which they start; instead yaws starts in the cluster master startup folder. 
Is this expected, or an issue with yaws? Happens with erlang R12, R13; yaws 1.77 and 1.82 (1.84 doesn't want to start in embedded mode).

I'm starting slave nodes with

slave:start_link(Host, NodeName, "-rsh ssh -pa /path/to/ebins -run file set_cwd /path/to/rundir -s myapp start -setcookie " ++ Cookie)
(Currently slave nodes are started on the same physical machine, but this may change later if it matters)

Also, this seems to change the CWD for the master node as well!?

Any pointers would be greatly appreciated.

Slobo