1CONDOR_WAIT(1)                  HTCondor Manual                 CONDOR_WAIT(1)
2
3
4

NAME

6       condor_wait - HTCondor Manual
7
8       Wait for jobs to finish
9
10

SYNOPSIS

12       condor_wait [-help | -version ]
13
14       condor_wait  [-debug  ]  [-status ] [-echo ] [-wait seconds] [-num num‐
15       ber-of-jobs] log-file [job ID ]
16

DESCRIPTION

18       condor_wait watches a job event log file (created with the log  command
19       within  a  submit  description  file) and returns when one or more jobs
20       from the log have completed or aborted.
21
22       Because condor_wait expects to find at least one job submitted event in
23       the  log  file,  at least one job must have been successfully submitted
24       with condor_submit before condor_wait is executed.
25
26       condor_wait will wait forever for jobs to finish, unless a shorter wait
27       time is specified.
28

OPTIONS

30          -help  Display usage information
31
32          -version
33                 Display version information
34
35          -debug Show extra debugging information.
36
37          -status
38                 Show job start and terminate information.
39
40          -echo  Print the events out to stdout.
41
42          -wait seconds
43                 Wait  no more than the integer number of seconds. The default
44                 is unlimited time.
45
46          -num number-of-jobs
47                 Wait for the integer number-of-jobs jobs to end. The  default
48                 is all jobs in the log file.
49
50          log file
51                 The  name  of the log file to watch for information about the
52                 job.
53
54          job ID A specific job or set of jobs to watch.
55                  If the job ID is only the job ClassAd  attribute  ClusterId,
56                 then condor_wait waits for all jobs with the given ClusterId.
57                 If the job ID is a pair of the job ClassAd attributes,  given
58                 by  ClusterId.ProcId, then condor_wait waits for the specific
59                 job with this job ID.  If this option is not  specified,  all
60                 jobs  that  exist in the log file when condor_wait is invoked
61                 will be watched.
62

GENERAL REMARKS

64       condor_wait is an inexpensive way to test or wait for the completion of
65       a job or a whole cluster, if you are trying to get a process outside of
66       HTCondor to synchronize with a job or set of jobs.
67
68       It can also be used to wait for the completion of a limited  subset  of
69       jobs, via the -num option.
70

EXAMPLES

72          condor_wait logfile
73
74       This command waits for all jobs that exist in logfile to complete.
75
76          condor_wait logfile 40
77
78       This  command waits for all jobs that exist in logfile with a job Clas‐
79       sAd attribute ClusterId of 40 to complete.
80
81          condor_wait -num 2 logfile
82
83       This command waits for any two jobs that exist in logfile to complete.
84
85          condor_wait logfile 40.1
86
87       This command waits for job 40.1 that exists in logfile to complete.
88
89          condor_wait -wait 3600 logfile 40.1
90
91       This waits for job 40.1 to complete by watching logfile,  but  it  will
92       not wait more than one hour (3600 seconds).
93

EXIT STATUS

95       condor_wait  exits with 0 if and only if the specified job or jobs have
96       completed or aborted. condor_wait returns 1 if unrecoverable errors oc‐
97       cur,  such  as a missing log file, if the job does not exist in the log
98       file, or the user-specified waiting time has expired.
99

AUTHOR

101       HTCondor Team
102

104       1990-2022, Center for High Throughput Computing, Computer Sciences  De‐
105       partment,  University  of  Wisconsin-Madison, Madison, WI, US. Licensed
106       under the Apache License, Version 2.0.
107
108
109
110
1118.8                              Jun 13, 2022                   CONDOR_WAIT(1)
Impressum