[torquedev] "complete" jobs behavior

Glen Beane glen.beane at gmail.com
Mon Feb 1 11:17:21 MST 2010


On Mon, Feb 1, 2010 at 1:04 PM, Garrick <garrick at usc.edu> wrote:

> On Mon, Feb 01, 2010 at 12:03:54PM -0500, Glen Beane alleged:
> > On Mon, Feb 1, 2010 at 11:45 AM, Garrick <garrick at usc.edu> wrote:
> >
> > > The purpose of "complete" is so the scheduled can read why a job has
> > > exited. For that end, the current behavior is correct.
> > >
> >
> > I can see a running job that gets qdeled end up in the "complete" state
> so
> > the scheduler can see why the job exited, but doesn't it seem strange to
> > qdel a job that is in the Q state and have it go to the C state?
>
> It's for the scheduler guys, so it's up to them.
>
>

fair enough
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.supercluster.org/pipermail/torquedev/attachments/20100201/13a1adc4/attachment.html 


More information about the torquedev mailing list