[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] "condor_suspend"


I like your idea.  I can't think of any reason why it wouldn't work.

I also happen to have wanted this feature, and since I was messing around with Condor's COD feature at the time, I implemented it using COD. (COD stands for "Computing On Demand" because it gives an application quick access to a node, suspending whatever other job is running there. The use of it purely for suspension purposes is more like "Computing Off Demand".)

Here's my script, in case it is helpful to you:


To make it work, you would need to configure VALID_COD_USERS and you would need to enable some method of user authentication (e.g. add a grid-mapfile). If you haven't already got that, it might be simpler to go with your idea and use condor_config_val, which relies on the administrative authorization settings instead.


Preston Smith wrote:

I'd like to be able to run a command on a node to suspend all the jobs on it, much like when I run condor_vacate to get them all out. I'll call it "condor_suspend" since that doesn't seem to exist.

My first idea on how to do this is to change SUSPEND:

SUSPEND = ( $(KeyboardBusy) || \
                 ( (CpuBusyTime > 2 * $(MINUTE)) \
&& $(ActivationTimer) > 90 ) ) || SuspendMeNow == TRUE

and then something in the reverse for CONTINUE.

My script could then twiddle SuspendMeNow with condor_config_val.

Has anybody else done this before and is willing to share?  :)
Is there a smarter way?


Preston Smith    <psmith@xxxxxxxxxx>
Systems Research Engineer
Rosen Center for Advanced Computing, Purdue University

Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at either