1condor_run(1)               General Commands Manual              condor_run(1)
2
3
4

Name

6       condor_runSubmit a shell command-line as an HTCondor job
7

Synopsis

9       condor_run[-u universe] [-a submitcmd] "shell command"
10

Description

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
17       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
23       % condor_run "myprog < input.data"
24
25       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
29       Specialized environment variables may be used to  specify  requirements
30       for the machine where the job may run.
31
32       CONDOR_ARCH
33
34          Specifies  the architecture of the required platform. Values will be
35          the same as the Archmachine ClassAd attribute.
36
37
38
39       CONDOR_OPSYS
40
41          Specifies the operating system of the required platform. Values will
42          be the same as the OpSysmachine ClassAd attribute.
43
44
45
46       CONDOR_REQUIREMENTS
47
48          Specifies  any  additional  requirements for the HTCondor job. It is
49          recommended  that  the  value  defined   for   CONDOR_REQUIREMENTSbe
50          enclosed in parenthesis.
51
52
53
54       When  one  or more of these environment variables is specified, the job
55       is submitted with:
56
57       Requirements = $CONDOR_REQUIREMENTS && Arch == $CONDOR_ARCH && \
58          OpSys == $CONDOR_OPSYS
59
60       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
64       All environment  variables  set  when  condor_runis  executed  will  be
65       included in the environment of the HTCondor job.
66
67       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

Options

71       -u universe
72
73          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
78
79
80       -a submitcmd
81
82          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
88
89
90
91

Examples

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
97       % setenv CONDOR_ARCH "SUN4u"
98       % setenv CONDOR_OPSYS "SOLARIS28"
99
100       Then, use condor_runto submit the compilation as in the following three
101       examples.
102
103       % condor_run "f77 -O -o myprog myprog.f"
104
105       or
106
107       % condor_run "make"
108
109       or
110
111       % condor_run "condor_compile cc -o myprog.condor myprog.c"
112

Files

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
118       .condor_run.<pid>
119
120          A shell script containing the shell command line.
121
122
123
124       .condor_submit.<pid>
125
126          The submit description file for the job.
127
128
129
130       .condor_log.<pid>
131
132          The HTCondor job's log file;  it  is  monitored  by  condor_run,  to
133          determine when the job exits.
134
135
136
137       .condor_out.<pid>
138
139          The output of the HTCondor job before it is output to the terminal.
140
141
142
143       .condor_error.<pid>
144
145          Any  error  messages  for the HTCondor job before they are output to
146          the terminal.
147
148          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

General Remarks

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
159       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
164       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
168       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
173       % perl path-to-condor/bin/condor_run "shell-cmd"
174

Exit Status

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

Author

182       Center   for   High   Throughput   Computing,   University  of  Wiscon‐
183       sin&ndash;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
190
191
192                                     date                        condor_run(1)
Impressum