1just-man-pages/condor_run(1)General Commands Manualjust-man-pages/condor_run(1)
2
6 condor_run Submit a shell command-line as a Condor job
7
9 condor_run [ -u universe ] shell command
10
12 condor_run bundles a shell command line into a Condor job and submits
13 the job. The condor_run command waits for the Condor job to complete,
14 writes the job's output to the terminal, and exits with the exit status
15 of the Condor 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 Condor 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 Condor job. It is rec‐
49 ommended that the value defined for CONDOR_REQUIREMENTSbe enclosed
50 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 && .br
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 Condor job.
66 condor_run removes the Condor job from the queue and deletes its tempo‐
68 rary files, if condor_run is killed before the Condor 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
83 condor_run may be used to compile an executable on a different plat‐
84 form. As an example, first set the environment variables for the
85 required platform:
86 % setenv CONDOR_ARCH "SUN4u"
88 % setenv CONDOR_OPSYS "SOLARIS28"
89 Then, use condor_run to submit the compilation as in the following
91 three examples.
92 % condor_run "f77 -O -o myprog myprog.f"
94 or
96 % condor_run "make"
98 or
100 % condor_run "condor_compile cc -o myprog.condor myprog.c"
102
104 condor_run creates the following temporary files in the user's working
105 directory. The placeholder <pid> is replaced by the process id of con‐
106 dor_run .
107 .condor_run.<pid>
109 A shell script containing the shell command line.
111 .condor_submit.<pid>
115 The submit description file for the job.
117 .condor_log.<pid>
121 The Condor job's log file; it is monitored by condor_run , to deter‐
123 mine when the job exits.
124 .condor_out.<pid>
128 The output of the Condor job before it is output to the terminal.
130 .condor_error.<pid>
134 Any error messages for the Condor job before they are output to the
136 terminal.
137 condor_run removes these files when the job completes. However, if
139 condor_run fails, it is possible that these files will remain in the
140 user's working directory, and the Condor job may remain in the
141 queue.
142
144 condor_run is intended for submitting simple shell command lines to
145 Condor. It does not provide the full functionality of condor_submit .
146 Therefore, some condor_submit errors and system failures may not be
147 handled correctly.
148 All processes specified within the single shell command line will be
150 executed on the single machine matched with the job. Condor will not
151 distribute multiple processes of a command line pipe across multiple
152 machines.
153 condor_run will use the shell specified in the SHELLenvironment vari‐
155 able, if one exists. Otherwise, it will use /bin/sh to execute the
156 shell command-line.
157 By default, condor_run expects Perl to be installed in /usr/bin/perl.
159 If Perl is installed in another path, ask the Condor administrator to
160 edit the path in the condor_run script, or explicitly call Perl from
161 the command line:
162 % perl path-to-condor/bin/condor_run "shell-cmd"
164
166 condor_run exits with a status value of 0 (zero) upon complete success.
167 The exit status of condor_run will be non-zero upon failure. The exit
168 status in the case of a single error due to a system call will be the
169 error number (errno) of the failed call.
170
172 Condor Team, University of Wisconsin-Madison
173
175 Copyright (C) 1990-2009 Condor Team, Computer Sciences Department, Uni‐
176 versity of Wisconsin-Madison, Madison, WI. All Rights Reserved.
177 Licensed under the Apache License, Version 2.0.
178 See the Condor Version 7.4.2 Manual or http://www.condorpro‐
180 ject.org/licensefor additional notices. condor-admin@cs.wisc.edu
181 date just-man-pages/condor_run(1)