condor_wait
Wait for HTCondor jobs to finish.
Synopsis
condor_wait [-help | -version]
condor_wait [-debug] [-status] [-echo] [-wait seconds] [-num number-of-jobs] log-file [job-ID]
Description
condor_wait watches a job event log file (created with the log command within a submit description file) and returns when one or more jobs from the log have completed or aborted.
Because condor_wait expects to find at least one job submitted event in the log file, at least one job must have been successfully submitted with condor_submit before condor_wait is executed.
condor_wait will wait forever for jobs to finish, unless a shorter wait time is specified.
Options
- -help
Display usage information.
- -version
Display version information.
- -debug
Show extra debugging information.
- -status
Show job start and terminate information.
- -echo
Print the events out to
stdout.- -wait seconds
Wait no more than the integer number of seconds. The default is unlimited time.
- -num number-of-jobs
Wait for the integer number-of-jobs jobs to end. The default is all jobs in the log file.
- -allevents
Continue reading the log even after all jobs have ended. Most useful in combination with -echo to transcribe an entire job event log to standard output. May not be combined with -num.
- log-file
The name of the log file to watch for information about the job.
- job-ID
A specific job or set of jobs to watch. If the job-ID is only the job ClassAd attribute ClusterId, then condor_wait waits for all jobs with the given ClusterId. If the job-ID is a pair of the job ClassAd attributes, given by ClusterId.ProcId, then condor_wait waits for the specific job with this job-ID. If this option is not specified, all jobs that exist in the log file when condor_wait is invoked will be watched.
General Remarks
condor_wait is an inexpensive way to test or wait for the completion of a job or a whole cluster, if you are trying to get a process outside of HTCondor to synchronize with a job or set of jobs.
It can also be used to wait for the completion of a limited subset of jobs, via the -num option.
Examples
Wait for all jobs in a log file to complete:
$ condor_wait logfile
Wait for all jobs in cluster 40 to complete:
$ condor_wait logfile 40
Wait for any two jobs to complete:
$ condor_wait -num 2 logfile
Wait for a specific job to complete:
$ condor_wait logfile 40.1
Wait for job 40.1 with a one hour timeout:
$ condor_wait -wait 3600 logfile 40.1
Exit Status
0 - Success (specified job or jobs have completed or aborted)
1 - Failure (unrecoverable errors such as missing log file, non-existent job, or timeout expired)
See Also
Availability
Linux, MacOS, Windows