Scroll to navigation

CONDOR_NOW(1) HTCondor Manual CONDOR_NOW(1)

NAME

condor_now - HTCondor Manual

Start a job now by vacating a currently running job.

SYNOPSIS

condor_now [-help]

condor_now [-name scheddname] [-pool hostname[:portnumber]] [-debug] now-job vacate-job [vacate-job ...]

DESCRIPTION

condor_now tries to run the now-job immediately. The vacate-job is immediately vacated; after it terminates, if the schedd still has the claim to the vacated job's slot - and it usually will - the schedd will immediately start the now-job on that slot.

If you specify multiple vacate-job s, each will be immediately vacated; after they all terminate, the schedd will try to coalesce their slots into a single, larger, slot and then use that slot to run the now-job.

You must specify each job using both the cluster and proc IDs (e.g., 123.4).

OPTIONS

Display usage information.
Print debugging output. Control the verbosity with the environment variable _CONDOR_TOOL_DEBUG, as usual.
Specify the scheduler by name.
Specify the pool to find the schedd in.
The job ID (cluster.proc) of the job to start immediately.
The job ID (cluster.proc) of one or more jobs to vacate.



GENERAL REMARKS

The now-job and the vacate-job must have the same owner; if you are not the queue super-user, you must own both jobs. The jobs must be on the same schedd, and both jobs must be in the vanilla universe. The now-job must be idle and the vacate-job must be running.

condor_now does not guarantee that the now-job will run immediately, as other factors (such as RANK <href="../admin-manual/configuration/startd.html#RANK"> expressions or other jobs from the same user) may affect scheduling decisions.

EXAMPLES

Start job 17.3 using job 4.2's slot:

$ condor_now 17.3 4.2


Debug why a job won't start on the 'magic' scheduler in the 'gandalf' pool:

$ export _CONDOR_TOOL_DEBUG=D_FULLDEBUG
$ condor_now -debug -name magic -pool gandalf 17.3 4.2


Start job 100.0 by coalescing slots from jobs 10.0 and 11.0:

$ condor_now 100.0 10.0 11.0


EXIT STATUS

0 - Success (schedd accepted the request to vacate and start the job)

1 - Failure

Note:

condor_now returns immediately after the schedd accepts the request. It does not wait for the now-job to actually start running.


SEE ALSO

condor_vacate_job <href="../man-pages/condor_vacate_job.html">, condor_q <href="../man-pages/condor_q.html">, condor_prio <href="../man-pages/condor_prio.html">

AVAILABILITY

Linux, MacOS, Windows

Author

HTCondor Team

Copyright

1990-2026, Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0.

May 12, 2026