1condor_run(1) General Commands Manual condor_run(1)
2
6 condor_runSubmit a shell command-line as an HTCondor job
7
9 condor_run[-u universe] [-a submitcmd] "shell command"
10
12 condor_runbundles a shell command line into an HTCondor job and submits
13 the job. The condor_runcommand waits for the HTCondor job to complete,
14 writes the job's output to the terminal, and exits with the exit status
15 of the HTCondor job. No output appears until the job completes.
16 Enclose the shell command line in double quote marks, so it may be
18 passed to condor_runwithout modification. condor_runwill not read input
19 from the terminal while the job executes. If the shell command line
20 requires input, redirect the input from a file, as illustrated by the
21 example
22 % condor_run "myprog < input.data"
24 condor_runjobs rely on a shared file system for access to any necessary
26 input files. The current working directory of the job must be accessi‐
27 ble to the machine within the HTCondor pool where the job runs.
28 Specialized environment variables may be used to specify requirements
30 for the machine where the job may run.
31 CONDOR_ARCH
33 Specifies the architecture of the required platform. Values will be
35 the same as the Archmachine ClassAd attribute.
36 CONDOR_OPSYS
40 Specifies the operating system of the required platform. Values will
42 be the same as the OpSysmachine ClassAd attribute.
43 CONDOR_REQUIREMENTS
47 Specifies any additional requirements for the HTCondor job. It is
49 recommended that the value defined for CONDOR_REQUIREMENTSbe
50 enclosed in parenthesis.
51 When one or more of these environment variables is specified, the job
55 is submitted with:
56 Requirements = $CONDOR_REQUIREMENTS && Arch == $CONDOR_ARCH && \
58 OpSys == $CONDOR_OPSYS
59 Without these environment variables, the job receives the default
61 requirements expression, which requests a machine of the same platform
62 as the machine on which condor_runis executed.
63 All environment variables set when condor_runis executed will be
65 included in the environment of the HTCondor job.
66 condor_runremoves the HTCondor job from the queue and deletes its tem‐
68 porary files, if condor_runis killed before the HTCondor job completes.
69
71 -u universe
72 Submit the job under the specified universe. The default is vanilla.
74 While any universe may be specified, only the vanilla, standard,
75 scheduler, and local universes result in a submit description file
76 that may work properly.
77 -a submitcmd
81 Add the specified submit command to the implied submit description
83 file for the job. To include spaces within submitcmd, enclose the
84 submit command in double quote marks. And, to include double quote
85 marks within submitcmd, enclose the submit command in single quote
86 marks.
87
93 condor_runmay be used to compile an executable on a different platform.
94 As an example, first set the environment variables for the required
95 platform:
96 % setenv CONDOR_ARCH "SUN4u"
98 % setenv CONDOR_OPSYS "SOLARIS28"
99 Then, use condor_runto submit the compilation as in the following three
101 examples.
102 % condor_run "f77 -O -o myprog myprog.f"
104 or
106 % condor_run "make"
108 or
110 % condor_run "condor_compile cc -o myprog.condor myprog.c"
112
114 condor_runcreates the following temporary files in the user's working
115 directory. The placeholder <pid> is replaced by the process id of con‐
116 dor_run.
117 .condor_run.<pid>
119 A shell script containing the shell command line.
121 .condor_submit.<pid>
125 The submit description file for the job.
127 .condor_log.<pid>
131 The HTCondor job's log file; it is monitored by condor_run, to
133 determine when the job exits.
134 .condor_out.<pid>
138 The output of the HTCondor job before it is output to the terminal.
140 .condor_error.<pid>
144 Any error messages for the HTCondor job before they are output to
146 the terminal.
147 condor_runremoves these files when the job completes. However, if
149 condor_runfails, it is possible that these files will remain in the
150 user's working directory, and the HTCondor job may remain in the
151 queue.
152
154 condor_runis intended for submitting simple shell command lines to
155 HTCondor. It does not provide the full functionality of condor_submit.
156 Therefore, some condor_submiterrors and system failures may not be han‐
157 dled correctly.
158 All processes specified within the single shell command line will be
160 executed on the single machine matched with the job. HTCondor will not
161 distribute multiple processes of a command line pipe across multiple
162 machines.
163 condor_runwill use the shell specified in the SHELLenvironment vari‐
165 able, if one exists. Otherwise, it will use /bin/shto execute the shell
166 command-line.
167 By default, condor_runexpects Perl to be installed in /usr/bin/perl. If
169 Perl is installed in another path, ask the Condor administrator to edit
170 the path in the condor_runscript, or explicitly call Perl from the com‐
171 mand line:
172 % perl path-to-condor/bin/condor_run "shell-cmd"
174
176 condor_runexits with a status value of 0 (zero) upon complete success.
177 The exit status of condor_runwill be non-zero upon failure. The exit
178 status in the case of a single error due to a system call will be the
179 error number (errno) of the failed call.
180
182 Center for High Throughput Computing, University of Wiscon‐
183 sin–Madison
184
186 Copyright © 1990-2019 Center for High Throughput Computing, Computer
187 Sciences Department, University of Wisconsin-Madison, Madison, WI. All
188 Rights Reserved. Licensed under the Apache License, Version 2.0.
189 date condor_run(1)