1just-man-pages/condor_run(1)General Commands Manualjust-man-pages/condor_run(1)
2
6 condor_run Submit a shell command-line as an HTCondor job
7
9 condor_run [ -u universe ] [ -a submitcmd ] shell command
10
12 condor_run bundles a shell command line into an HTCondor job and sub‐
13 mits the job. The condor_run command waits for the HTCondor job to com‐
14 plete, writes the job's output to the terminal, and exits with the exit
15 status 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_run without modification. condor_run will not read
19 input from the terminal while the job executes. If the shell command
20 line requires input, redirect the input from a file, as illustrated by
21 the example
22 % condor_run "myprog < input.data"
24 condor_run jobs rely on a shared file system for access to any neces‐
26 sary input files. The current working directory of the job must be
27 accessible 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 Arch machine ClassAd attribute.
36 CONDOR_OPSYS
40 Specifies the operating system of the required platform. Values will
42 be the same as the OpSys machine ClassAd attribute.
43 CONDOR_REQUIREMENTS
47 Specifies any additional requirements for the HTCondor job. It is
49 recommended that the value defined for CONDOR_REQUIREMENTS be
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_run is executed.
63 All environment variables set when condor_run is executed will be
65 included in the environment of the HTCondor job.
66 condor_run removes the HTCondor job from the queue and deletes its tem‐
68 porary files, if condor_run is killed before the HTCondor job com‐
69 pletes.
70
72 -u universe
73 Submit the job under the specified universe. The default is vanilla.
75 While any universe may be specified, only the vanilla, standard,
76 scheduler, and local universes result in a submit description file
77 that may work properly.
78 -a submitcmd
82 Add the specified submit command to the implied submit description
84 file for the job. To include spaces within submitcmd , enclose the
85 submit command in double quote marks. And, to include double quote
86 marks within submitcmd , enclose the submit command in single quote
87 marks.
88
94 condor_run may be used to compile an executable on a different plat‐
95 form. As an example, first set the environment variables for the
96 required platform:
97 % setenv CONDOR_ARCH "SUN4u"
99 % setenv CONDOR_OPSYS "SOLARIS28"
100 Then, use condor_run to submit the compilation as in the following
102 three examples.
103 % condor_run "f77 -O -o myprog myprog.f"
105 or
107 % condor_run "make"
109 or
111 % condor_run "condor_compile cc -o myprog.condor myprog.c"
113
115 condor_run creates the following temporary files in the user's working
116 directory. The placeholder <pid> is replaced by the process id of con‐
117 dor_run .
118 .condor_run.<pid>
120 A shell script containing the shell command line.
122 .condor_submit.<pid>
126 The submit description file for the job.
128 .condor_log.<pid>
132 The HTCondor job's log file; it is monitored by condor_run , to
134 determine when the job exits.
135 .condor_out.<pid>
139 The output of the HTCondor job before it is output to the terminal.
141 .condor_error.<pid>
145 Any error messages for the HTCondor job before they are output to
147 the terminal.
148 condor_run removes these files when the job completes. However, if
150 condor_run fails, it is possible that these files will remain in the
151 user's working directory, and the HTCondor job may remain in the
152 queue.
153
155 condor_run is intended for submitting simple shell command lines to
156 HTCondor. It does not provide the full functionality of condor_submit .
157 Therefore, some condor_submit errors and system failures may not be
158 handled correctly.
159 All processes specified within the single shell command line will be
161 executed on the single machine matched with the job. HTCondor will not
162 distribute multiple processes of a command line pipe across multiple
163 machines.
164 condor_run will use the shell specified in the SHELL environment vari‐
166 able, if one exists. Otherwise, it will use /bin/sh to execute the
167 shell command-line.
168 By default, condor_run expects Perl to be installed in /usr/bin/perl .
170 If Perl is installed in another path, ask the Condor administrator to
171 edit the path in the condor_run script, or explicitly call Perl from
172 the command line:
173 % perl path-to-condor/bin/condor_run "shell-cmd"
175
177 condor_run exits with a status value of 0 (zero) upon complete success.
178 The exit status of condor_run will be non-zero upon failure. The exit
179 status in the case of a single error due to a system call will be the
180 error number ( errno ) of the failed call.
181
183 Center for High Throughput Computing, University of Wisconsin-Madison
184
186 Copyright (C) 1990-2018 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 just-man-pages/condor_run(1)