I think my question has been answered:<div><br></div><div><a href="http://gmod.827538.n3.nabble.com/NFS-Cluster-and-working-directories-questions-td3784165.html">http://gmod.827538.n3.nabble.com/NFS-Cluster-and-working-directories-questions-td3784165.html</a> </div>
<div><br></div><div>Hopefully can see the e<span style="font-family:Verdana,Geneva,Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">nhancements in the near future.</span><br><br>Cheers.</div><div>
Derrick<br><br><div class="gmail_quote">On Tue, Jun 19, 2012 at 5:01 PM, Derrick Lin <span dir="ltr">&lt;<a href="mailto:klin938@gmail.com" target="_blank">klin938@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi guys,<div><br></div><div>I have deploy a galaxy on a cluster (so I installed it on a NFS share that it&#39;s accessible by all cluster compute nodes).</div><div><br></div><div>Everything is running fine. Now I am looking for a way such that every job dispatched to a compute node uses that node&#39;s local /tmp as working directory.</div>

<div><br></div><div>I know galaxy config provides job_working_directory for the similar purpose.  </div><div><br></div><div>My question really is, while all my compute nodes can access the NFS share where galaxy installed, but the galaxy host cannot access each compute node&#39;s /tmp.</div>

<div><br></div><div>Is there a way that for the galaxy to collect job results back to the data directory?</div><div><br></div><div>Regards,</div><div>Derrick</div>
</blockquote></div><br></div>