.\"Man page for condor_wait 
.\"Generated by makeman on Tue May 29 00:38:53 2018
.TH condor_wait  1 "May 2018"
.SH Name
.P
condor_wait Wait \- for jobs to finish 
.P

.P
.SH Synopsis
condor_wait [-help -version] 
.P
condor_wait[-debug] [-status] [-echo] [-wait seconds] [-num number-of-jobs] log-file[job ID] 
.P
.SH Description
.P
condor_waitwatches a job event log file (created with the logcommand within a submit description file) and returns when one or more jobs from the log have completed or aborted. 
.P
Because condor_waitexpects to find at least one job submitted event in the log file, at least one job must have been successfully submitted with condor_submitbefore condor_waitis executed. 
.P
condor_waitwill wait forever for jobs to finish, unless a shorter wait time is specified. 
.P
.SH Options
.P

.B -help
.IP "" 3
Display usage information 
.IP "" 3
.P
.B -version
.IP "" 3
Display version information 
.IP "" 3
.P
.B -debug
.IP "" 3
Show extra debugging information. 
.IP "" 3
.P
.B -status
.IP "" 3
Show job start and terminate information. 
.IP "" 3
.P
.B -echo
.IP "" 3
Print the events out to  stdout . 
.IP "" 3
.P
.B -wait seconds
.IP "" 3
Wait no more than the integer number of seconds. The default is unlimited time. 
.IP "" 3
.P
.B -num number-of-jobs
.IP "" 3
Wait for the integer number-of-jobsjobs to end. The default is all jobs in the log file. 
.IP "" 3
.P
.B log file
.IP "" 3
The name of the log file to watch for information about the job. 
.IP "" 3
.P
.B job ID
.IP "" 3
A specific job or set of jobs to watch. If the job IDis only the job ClassAd attribute  ClusterId , then condor_wait waits for all jobs with the given  ClusterId . If the job IDis 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. 
.IP "" 3
.IP "" 3
.P

.SH General Remarks
.P
condor_waitis 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. 
.P
It can also be used to wait for the completion of a limited subset of jobs, via the -numoption. 
.P
.SH Examples
.P


.br
condor_wait  logfile
.P
This command waits for all jobs that exist in  logfile to complete. 
.P


.br
condor_wait  logfile 40
.P
This command waits for all jobs that exist in  logfile with a job ClassAd attribute  ClusterId of 40 to complete. 
.P


.br
condor_wait  -num 2 logfile
.P
This command waits for any two jobs that exist in  logfile to complete. 
.P


.br
condor_wait  logfile 40.1
.P
This command waits for job 40.1 that exists in  logfile to complete. 
.P


.br
condor_wait  -wait 3600 logfile 40.1
.P
This waits for job 40.1 to complete by watching  logfile , but it will not wait more than one hour (3600 seconds). 
.P
.SH Exit Status
.P
condor_waitexits with 0 if and only if the specified job or jobs have completed or aborted. condor_waitreturns 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. 
.P
.SH Author
Center for High Throughput Computing, University of Wisconsin-Madison 
.SH Copyright
Copyright (C) 1990-2016 Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. Licensed under the Apache License, Version 2.0.