[torquedev] jobs owners purging own jobs?

Garrick Staples garrick at usc.edu
Thu Feb 23 23:57:17 MST 2006

On Thu, Feb 23, 2006 at 11:28:16PM -0500, Caird, Andrew J alleged:
> Thanks Garrick,
> What makes it dangerous, and can it be made safer?  I'm willing to give
> a try if it's possible.

qdel -p simply tells pbs_server to purge everything it knows about the
job, without talking to MS.  The dangerous part is that it doesn't talk
to MS.  The job may possibly still be running, epilogue scripts may still
be run, and possibly random processes are going to get killed.  It is
basicly intentionally breaking the entire job state machine and is only
a last resort to removing a job.

This functionality should not be needed by users.  If you frequently
find that jobs aren't killable, then maybe that is something we need to

> My goal is to keep funtionality we had with PBSPro ('-W force').

I don't know PBSPro, but I doubt a user-accessible -W force is
equivalent to -p.

> Thanks.
> --andy
>  -----Original Message-----
> From: 	Garrick Staples [mailto:garrick at usc.edu]
> Sent:	Thu Feb 23 22:59:24 2006
> To:	torquedev at supercluster.org
> Subject:	Re: [torquedev] jobs owners purging own jobs?
> On Thu, Feb 23, 2006 at 10:45:15PM -0500, Andrew J Caird alleged:
> > 
> > Is there some reason that the job owner can use the purge ('-p')
> option on 
> > his own jobs?  For us this would be handy, so I've added a server
> setting 
> Yes, because -p is very dangerous.  It should only be used when the
> job's execution node has died and isn't coming back and there is no
> other way to remove the job.  It is an administrative decision.
> -- 
> Garrick Staples, Linux/HPCC Administrator
> University of Southern California

Garrick Staples, Linux/HPCC Administrator
University of Southern California
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torquedev/attachments/20060223/00aa7b75/attachment.bin

More information about the torquedev mailing list