On Thu, Apr 07, 2011 at 05:05:04PM -0600, Ken Nielson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">There is a new snapshot for 2.5.6 available. This fixes a problem with
a patch for Bugzilla 116 where the new resource procct was added. If the
-l nodes option was not used in a job submission then the job would not
be run by Moab because procct was added to the Resource_List attribute
and treated like a generic resource by Moab. Because the generic resource
procct does not exist Moab never schedules the job.

This is now fixed.

You can download this snapshot at <a class="moz-txt-link-freetext" href="http://www.clusterresources.com/downloads/torque/snapshots/torque-2.5.6-snap.201104071657.tar.gz">http://www.clusterresources.com/downloads/torque/snapshots/torque-2.5.6-snap.201104071657.tar.gz</a>

Please download and let us know if you find any problems.
</pre>
</blockquote>
<pre wrap="">
I am afraid this does not work: I haven't traced this back to the
source routine, but apparently this new version presets the nodes
resource to 1, correct?
Thus, if a user only requests -l procs=N, with 2.5.6-snap.201104071657
procct is set to N+1, not N, see

torque-2.5.6-snap.201104041023 actually worked flawlessly for me.
Which means that I haven't figured out how to trigger the bug that
torque-2.5.6-snap.201104071657 was supposed to fix.
Regardless of whether I specified -l nodes=... or -l procs=... or
neither moab always started my job, i.e., the procct resource
always got removed before the job was sent to moab, see,