1condor_wait(1) General Commands Manual condor_wait(1)
2
3
4
6 condor_waitWait for jobs to finish
7
9 condor_wait[-help | -version]
10
11 condor_wait[-debug] [-status] [-echo] [-wait seconds] [-num number-of-
12 jobs] log-file[job ID]
13
15 condor_waitwatches a job event log file (created with the logcommand
16 within a submit description file) and returns when one or more jobs
17 from the log have completed or aborted.
18
19 Because condor_waitexpects to find at least one job submitted event in
20 the log file, at least one job must have been successfully submitted
21 with condor_submitbefore condor_waitis executed.
22
23 condor_waitwill wait forever for jobs to finish, unless a shorter wait
24 time is specified.
25
27 -help
28
29 Display usage information
30
31
32
33 -version
34
35 Display version information
36
37
38
39 -debug
40
41 Show extra debugging information.
42
43
44
45 -status
46
47 Show job start and terminate information.
48
49
50
51 -echo
52
53 Print the events out to stdout.
54
55
56
57 -wait seconds
58
59 Wait no more than the integer number of seconds. The default is
60 unlimited time.
61
62
63
64 -num number-of-jobs
65
66 Wait for the integer number-of-jobsjobs to end. The default is all
67 jobs in the log file.
68
69
70
71 log file
72
73 The name of the log file to watch for information about the job.
74
75
76
77 job ID
78
79 A specific job or set of jobs to watch. If the job IDis only the job
80 ClassAd attribute ClusterId, then condor_waitwaits for all jobs with
81 the given ClusterId. If the job IDis a pair of the job ClassAd
82 attributes, given by ClusterId.ProcId, then condor_waitwaits for the
83 specific job with this job ID. If this option is not specified, all
84 jobs that exist in the log file when condor_waitis invoked will be
85 watched.
86
87
88
89
90
92 condor_waitis an inexpensive way to test or wait for the completion of
93 a job or a whole cluster, if you are trying to get a process outside of
94 HTCondor to synchronize with a job or set of jobs.
95
96 It can also be used to wait for the completion of a limited subset of
97 jobs, via the -numoption.
98
100 condor_wait logfile This command waits for all jobs that exist in log‐
101 fileto complete.
102
103 condor_wait logfile 40 This command waits for all jobs that exist in
104 logfilewith a job ClassAd attribute ClusterIdof 40 to complete.
105
106 condor_wait -num 2 logfile This command waits for any two jobs that
107 exist in logfileto complete.
108
109 condor_wait logfile 40.1 This command waits for job 40.1 that exists in
110 logfileto complete.
111
112 condor_wait -wait 3600 logfile 40.1 This waits for job 40.1 to complete
113 by watching logfile, but it will not wait more than one hour (3600 sec‐
114 onds).
115
117 condor_waitexits with 0 if and only if the specified job or jobs have
118 completed or aborted. condor_waitreturns 1 if unrecoverable errors
119 occur, such as a missing log file, if the job does not exist in the log
120 file, or the user-specified waiting time has expired.
121
123 Center for High Throughput Computing, University of Wiscon‐
124 sin–Madison
125
127 Copyright © 1990-2019 Center for High Throughput Computing, Computer
128 Sciences Department, University of Wisconsin-Madison, Madison, WI. All
129 Rights Reserved. Licensed under the Apache License, Version 2.0.
130
131
132
133 date condor_wait(1)