Would the prologue/epilogue scripts be able to be set system wide? or would each job need them included? We've got quite a few users on our systems, so having each of them include this would be a bit difficult.<br><br>
Cheers,<br>-Nick<br><br><div class="gmail_quote">On Tue, May 20, 2008 at 2:49 PM, Tom Rudwick <<a href="mailto:tomr@intrinsity.com">tomr@intrinsity.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
One way is to use prolog/epilogue scripts to start and stop your<br>
service.<br>
<br>
Tom<br>
<br>
<br>
Nicholas Geraedts wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">
Hello everyone,<br>
<br>
I was wondering if it might be possible to setup a system that would start/stop a service on the compute nodes based on whether they had a job that was submitted to them. I'm not sure if this is best setup on the compute nodes, or rather that this should be controlled by the headnode. The service would likely start a process that takes up the system resources, however, so I'm not sure how this would work in conjunction with the load-monitoring of Maui/Torque.<br>
<br>
Any thoughts/advice would be much appreciated!<br>
<br>
Cheers,<br>
-Nick<br>
<br>
<br></div></div>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
mauiusers mailing list<br>
<a href="mailto:mauiusers@supercluster.org" target="_blank">mauiusers@supercluster.org</a><br>
<a href="http://www.supercluster.org/mailman/listinfo/mauiusers" target="_blank">http://www.supercluster.org/mailman/listinfo/mauiusers</a><br>
</blockquote>
<br>
</blockquote></div><br>