condor_wait [-debug] [-wait seconds] [-num number-of-jobs] log-file [job ID]
condor_wait watches a user 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.
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 Condor 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.
condor_wait logfileThis command waits for all jobs that exist in logfile to complete.
condor_wait logfile 40This command waits for all jobs that exist in logfile with a job ClassAd attribute ClusterId of 40 to complete.
condor_wait -num 2 logfileThis command waits for any two jobs that exist in logfile to complete.
condor_wait logfile 40.1This command waits for job 40.1 that exists in logfile to complete.
condor_wait -wait 3600 logfile 40.1This waits for job 40.1 to complete by watching logfile, but it will not wait more than one hour (3600 seconds).
condor_wait exits with 0 if and only if the specified job or jobs have completed or aborted. condor_wait returns 1 if unrecoverable errors occur, such as a missing log file, if the job does not exist in the log file, or the user-specified waiting time has expired.
See the Condor Version 7.6.10 Manual or http://research.cs.wisc.edu/htcondor/ for additional notices.