1just-man-pages/condor_dagman(G1e)neral Commands Manjuuaslt-man-pages/condor_dagman(1)
2
6 condor_dagman meta scheduler of the jobs submitted as the nodes of a
7 DAG or DAGs
8
10 condor_dagman [ -debug level ] [ -rescue filename ] [ -maxidle num‐
11 berOfJobs ] [ -maxjobs numberOfJobs ] [ -maxpre NumberOfPREscripts ] [
12 -maxpost NumberOfPOSTscripts ] [ -noeventchecks ] [ -allowlogerror ] [
13 -usedagdir ] -lockfile filename [ -waitfordebug ] [ -autorescue 0|1 ] [
14 -dorescuefrom number ] -csdversion version_string [ -allowversionmis‐
15 match ] [ -DumpRescue ] -dag dag_file [ -dag dag_file_2 ... -dag
16 dag_file_n ]
17
19 condor_dagman is a meta scheduler for the Condor jobs within a DAG
20 (directed acyclic graph) (or multiple DAGs). In typical usage, a sub‐
21 mitter of jobs that are organized into a DAG submits the DAG using con‐
22 dor_submit_dag . condor_submit_dag does error checking on aspects of
23 the DAG and then submits condor_dagman as a Condor job. condor_dagman
24 uses log files to coordinate the further submission of the jobs within
25 the DAG.
26 As part of daemoncore , the set of command-line arguments given in sec‐
28 tion work for condor_dagman .
29 Arguments to condor_dagman are either automatically set by condor_sub‐
31 mit_dag or they are specified as command-line arguments to condor_sub‐
32 mit_dag and passed on to condor_dagman . The method by which the argu‐
33 ments are set is given in their description below.
34 condor_dagman can run multiple, independent DAGs. This is done by spec‐
36 ifying multiple -dag a rguments. Pass multiple DAG input files as com‐
37 mand-line arguments to condor_submit_dag .
38 Debugging output may be obtained by using the -debug level option.
40 Level values and what they produce is described as
41 * level = 0; never produce output, except for usage info
43 * level = 1; very quiet, output severe errors
45 * level = 2; normal output, errors and warnings
47 * level = 3; output errors, as well as all warnings
49 * level = 4; internal debugging output
51 * level = 5; internal debugging output; outer loop debugging
53 * level = 6; internal debugging output; inner loop debugging
55 * level = 7; internal debugging output; rarely used
57
59 -debug level
60 An integer level of debugging output. level is an integer, with
62 values of 0-7 inclusive, where 7 is the most verbose output. This
63 command-line option to condor_submit_dag is passed to condor_dagman
64 or defaults to the value 3, as set by condor_submit_dag .
65 -rescue filename
69 Sets the file name of the rescue DAG to write in the case of a fail‐
71 ure. As passed by condor_submit_dag , the name of the file will be
72 the name of the DAG input file concatenated with the string .rescue.
73 This argument is now optional, and in general it is preferred to not
74 specify it. This allows condor_dagman to automatically generate an
75 appropriate rescue DAG name.
76 -maxidle NumberOfJobs
80 Sets the maximum number of idle jobs allowed before condor_dagman
82 stops submitting more jobs. Once idle jobs start to run, condor_dag‐
83 man will resume submitting jobs. NumberOfJobs is a positive inte‐
84 ger. This command-line option to condor_submit_dag is passed to con‐
85 dor_dagman . If not specified, the number of idle jobs is unlimited.
86 -maxjobs numberOfJobs
90 Sets the maximum number of jobs within the DAG that will be submit‐
92 ted to Condor at one time. numberOfJobs is a positive integer. This
93 command-line option to condor_submit_dag is passed to condor_dagman
94 . If not specified, the default number of jobs is unlimited.
95 -maxpre NumberOfPREscripts
99 Sets the maximum number of PRE scripts within the DAG that may be
101 running at one time. NumberOfPREScripts is a positive integer. This
102 command-line option to condor_submit_dag is passed to condor_dagman
103 . If not specified, the default number of PRE scripts is unlimited.
104 -maxpost NumberOfPOSTscripts
108 Sets the maximum number of POST scripts within the DAG that may be
110 running at one time. NumberOfPOSTScripts is a positive integer.
111 This command-line option to condor_submit_dag is passed to con‐
112 dor_dagman . If not specified, the default number of POST scripts is
113 unlimited.
114 -noeventchecks
118 This argument is no longer used; it is now ignored. Its functional‐
120 ity is now implemented by the DAGMAN_ALLOW_EVENTSconfiguration macro
121 (see section ).
122 -allowlogerror
126 This optional argument has condor_dagman try to run the specified
128 DAG, even in the case of detected errors in the user log specifica‐
129 tion. As of version 7.3.2, this argument has an effect only on DAGs
130 containing Stork job nodes.
131 -usedagdir
135 This optional argument causes condor_dagman to run each specified
137 DAG as if the directory containing that DAG file was the current
138 working directory. This option is most useful when running multiple
139 DAGs in a single condor_dagman .
140 -lockfile filename
144 Names the file created and used as a lock file. The lock file pre‐
146 vents execution of two of the same DAG, as defined by a DAG input
147 file. A default lock file ending with the suffix .dag.lockis passed
148 to condor_dagman by condor_submit_dag .
149 -waitfordebug
153 This optional argument causes condor_dagman to wait at startup until
155 someone attaches to the process with a debugger and sets the
156 wait_for_debug variable in main_init() to false.
157 -autorescue 0|1
161 Whether to automatically run the newest rescue DAG for the given DAG
163 file, if one exists (0 = false, 1 = true).
164 -dorescuefrom number
168 Forces condor_dagman to run the specified rescue DAG number for the
170 given DAG. A value of 0 is the same as not specifying this option.
171 Specifying a non-existant rescue DAG is a fatal error.
172 -csdversion version_string
176 version_string is the version of the condor_submit_dag program. At
178 startup, condor_dagman checks for a version mismatch with the con‐
179 dor_submit_dag version in this argument.
180 -allowversionmismatch
184 This optional argument causes condor_dagman to allow a version mis‐
186 match between condor_dagman itself and the .condor.subfile produced
187 by condor_submit_dag (or, in other words, between condor_submit_dag
188 and condor_dagman ). WARNING! This option should be used only if
189 absolutely necessary. Allowing version mismatches can cause subtle
190 problems when running DAGs. (Note that, starting with version 7.4.0,
191 condor_dagman no longer requires an exact version match between
192 itself and the .condor.subfile. Instead, a "minimum compatible ver‐
193 sion" is defined, and any .condor.subfile of that version or newer
194 is accepted.)
195 -DumpRescue
199 This optional argument causes condor_dagman to immediately dump a
201 rescue DAG and then exit, as opposed to actually running the DAG.
202 (This feature is mainly intended for testing.)
203 -dag filename
207 filename is the name of the DAG input file that is set as an argu‐
209 ment to condor_submit_dag , and passed to condor_dagman .
210
214 condor_dagman will exit with a status value of 0 (zero) upon success,
215 and it will exit with the value 1 (one) upon failure.
216
218 condor_dagman is normally not run directly, but submitted as a Condor
219 job by running condor_submit_dag. See the condor_submit_dag manual page
220 for examples.
221
223 Condor Team, University of Wisconsin-Madison
224
226 Copyright (C) 1990-2009 Condor Team, Computer Sciences Department, Uni‐
227 versity of Wisconsin-Madison, Madison, WI. All Rights Reserved.
228 Licensed under the Apache License, Version 2.0.
229 See the Condor Version 7.4.2 Manual or http://www.condorpro‐
231 ject.org/licensefor additional notices. condor-admin@cs.wisc.edu
232 date just-man-pages/condor_dagman(1)