[torqueusers] Question to Torque community regarding display of completed jobs in qstat

[Craig Tierney - NOAA Affiliate]

On Tue, Dec 4, 2012 at 10:04 AM, Ken Nielson <knielson at adaptivecomputing.com
> wrote:

>
> On Mon, Dec 3, 2012 at 3:34 PM, <Gareth.Williams at csiro.au> wrote:
>
>> Hi Craig,****
>>
>> ** **
>>
>> I’ve seen others’ responses buy no-one has mentioned using showjobs to
>> return info on complete jobs.  It is a potentially useful piece of the
>> broader puzzle – though is not part of answering your specific question.*
>> ***
>>
>> ** **
>>
>> Gareth****
>>
>> ** **
>>
>> *From:* Craig Tierney - NOAA Affiliate [mailto:craig.tierney at noaa.gov]
>> *Sent:* Monday, 3 December 2012 5:24 AM
>> *To:* Torque Users Mailing List
>> *Subject:* [torqueusers] Question to Torque community regarding display
>> of completed jobs in qstat****
>>
>> ** **
>>
>> Hello all,****
>>
>> ** **
>>
>> I have a question for Torque users regarding the display of completed
>> jobs in qstat.  Do others find the listing of completed jobs by default via
>> qstat makes finding things in the output much more difficult and completely
>> unnecessary?  Having the completed jobs in qstat can significantly slow
>> down qstat if you have a lot (thousands) of completed jobs which is another
>> hassle.****
>>
>> ** **
>>
>> I asking this because I need to be able to get error codes from completed
>> jobs (for minutes to hours after completion).  To do this, they have to
>> still be in the queue.  This function is very important, but not to anyone
>> who runs qstat by hand.  Grid Engine had a way to get completed jobs, but
>> only when asked for.****
>>
>> ** **
>>
>> Thanks,****
>>
>> Craig****
>>
>> _______________________________________________
>> torqueusers mailing list
>> torqueusers at supercluster.org
>> http://www.supercluster.org/mailman/listinfo/torqueusers
>>
>>
> Is there a reason why just adding a command line switch to tell qstat not
> to display completed jobs is not acceptable?
>
> Ken
>
>
Ken,

This could work.  There are lots of things that could work.  My point is
that the default behavior doesn't have any value (except it already
exists).  I want the users (and myself) to do as little as possible.  I
asked the question in a way I hoped would discuss if anyone else is
bothered by the default behavior.  Maybe I am the only one that cares that
"qstat" generates too much information in a way that I think is unnecessary.

Craig



> _______________________________________________
> torqueusers mailing list
> torqueusers at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torqueusers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.supercluster.org/pipermail/torqueusers/attachments/20121204/7c01104f/attachment.html