Hi,<br><br><div class="gmail_quote">On 10 August 2012 20:31, MinRK <span dir="ltr"><<a href="mailto:benjaminrk@gmail.com" target="_blank">benjaminrk@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Let me start by saying that in simple NFS+SSH environments (which I use most often), I find ipcluster more trouble than it's worth, and tend to do the following, which requires zero config:</div><div><br></div><div>
[host0] $> ipcontroller --ip=* &</div><div>[host0] $> ssh host1 ipcluster engines -n 4</div></blockquote><div><br></div><div>OK, this is good enough for the time being, but it'd be really nice to be able to kill things cleanly. I find that otherwise, the slaves don't recognise changes in the code (ie they need a reload). At the moment I succeed by killing ssh sessions, not very elegant ;-)</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>This is yet another bug in ipcluster argument relaying, but if you change SSHEngineSetLauncher.remote_profile_dir to SSHEngineLauncher.remote_profile_dir, I think it should work. What you are doing definitely *should* work, and I will look into why it doesn't.</div>
</blockquote><div><br></div><div>Nope, doesn't work. I can't retest, as I'm actually using the cluster as above, but is there anything you'd like to know about my setup before I try again?</div><div><br></div>
<div>Thanks!</div><div>Jose</div></div>