[Moabusers] node locked GRES not appearing in checkjob

Brock Palen brockp at umich.edu
Fri Jul 6 16:14:19 MDT 2007


Great!
Thank you!

Brock Palen
Center for Advanced Computing
brockp at umich.edu
(734)936-1985


On Jul 6, 2007, at 5:12 PM, Douglas Wightman wrote:

> We have patched this and it will be available in the latest snapshot.
>
> - Douglas
>
> On Fri, 2007-07-06 at 13:38 -0400, Brock Palen wrote:
>> Oh in addition,
>>
>> In followup to my other mail, If i submit a job requesting a node
>> locked resource that resource does not appear in the checkjob
>> output.  Even when job is running or queued.
>>
>> It would be handy for jobs blocked to see that its requesting such a
>> resource.  It DOES show up if you use checkjob -v JOBID,
>> But thats like a sledge hammer of information.  It would be really
>> nice if GRES (application)  could be added to the following list:
>>
>> checkjob JOBID
>>
>> Req[0]  TaskCount: 1  Partition: nyx
>> Memory >= 0  Disk >= 0  Swap >= 0
>> Opsys:   ---  Arch: ---  Features: ---
>>
>> vs.
>> checkjob -v JOBID
>>
>> NodeAccess: ---
>> TasksPerNode: 1  Application: norman  NodeCount:  1
>>
>>
>> Thanks! (sorry forgot to include this is my last email)
>>
>> Brock Palen
>> Center for Advanced Computing
>> brockp at umich.edu
>> (734)936-1985
>>
>>
>> _______________________________________________
>> moabusers mailing list
>> moabusers at supercluster.org
>> http://www.supercluster.org/mailman/listinfo/moabusers
>
>
>



More information about the moabusers mailing list