<br><br><div class="gmail_quote">On Wed, Apr 16, 2008 at 11:52 AM, Jim Coyle <<a href="mailto:jjc@iastate.edu">jjc@iastate.edu</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;">
John,<br>
<br>
This is a function of the launcher.</blockquote><div><br>no, it's really a function of the job scheduler<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
I use mpirun and create a different machinefile.<br>
sort -u $PBSNODEFILE > ./tmp1<br>
cat tmp1 tmp1 > tmp2<br>
mpirun -np 4 -machinefile tmp2 ...<br>
</blockquote><div><br>using a machine file with torque is a bad idea. You should be using a TM based job launcher (OpenMPI and LAM have TM support, OSC's mpiexec provides it for mpich), and you should be submitting your job in such a way that the scheduler knows to schedule one task per node<br>
<br>as for the original poster: you can configure moab or maui to honor your explicit node request rather than pack multiple ppn=1 requests onto one node. I would try adding pmem to your resource request though, like brock requested <br>
</div></div><br>