condor_run - Submit a shell command-line as a Condor job
condor_run [ -u universe ] shell command
condor_run bundles a shell command line into a Condor job and submits
the job. The condor_run command waits for the Condor job to complete,
writes the job’s output to the terminal, and exits with the exit status
of the Condor job. No output appears until the job completes.
Enclose the shell command line in double quote marks, so it may be
passed to condor_run without modification. condor_run will not read
input from the terminal while the job executes. If the shell command
line requires input, redirect the input from a file, as illustrated by
% condor_run "myprog < input.data"
condor_run jobs rely on a shared file system for access to any
necessary input files. The current working directory of the job must be
accessible to the machine within the Condor pool where the job runs.
Specialized environment variables may be used to specify requirements
for the machine where the job may run.
Specifies the architecture of the required platform. Values will be
the same as the Archmachine ClassAd attribute.
Specifies the operating system of the required platform. Values will
be the same as the OpSysmachine ClassAd attribute.
Specifies any additional requirements for the Condor job. It is
recommended that the value defined for CONDOR_REQUIREMENTSbe
enclosed in parenthesis.
When one or more of these environment variables is specified, the job
is submitted with:
Requirements = $CONDOR_REQUIREMENTS && Arch == $CONDOR_ARCH && .br
OpSys == $CONDOR_OPSYS
Without these environment variables, the job receives the default
requirements expression, which requests a machine of the same platform
as the machine on which condor_run is executed.
All environment variables set when condor_run is executed will be
included in the environment of the Condor job.
condor_run removes the Condor job from the queue and deletes its
temporary files, if condor_run is killed before the Condor job
Submit the job under the specified universe. The default is vanilla.
While any universe may be specified, only the vanilla, standard,
scheduler, and local universes result in a submit description file
that may work properly.
condor_run may be used to compile an executable on a different
platform. As an example, first set the environment variables for the
% setenv CONDOR_ARCH "SUN4u"
% setenv CONDOR_OPSYS "SOLARIS28"
Then, use condor_run to submit the compilation as in the following
% condor_run "f77 -O -o myprog myprog.f"
% condor_run "make"
% condor_run "condor_compile cc -o myprog.condor myprog.c"
condor_run creates the following temporary files in the user’s working
directory. The placeholder <pid> is replaced by the process id of
A shell script containing the shell command line.
The submit description file for the job.
The Condor job’s log file; it is monitored by condor_run , to
determine when the job exits.
The output of the Condor job before it is output to the terminal.
Any error messages for the Condor job before they are output to the
condor_run removes these files when the job completes. However, if
condor_run fails, it is possible that these files will remain in the
user’s working directory, and the Condor job may remain in the
condor_run is intended for submitting simple shell command lines to
Condor. It does not provide the full functionality of condor_submit .
Therefore, some condor_submit errors and system failures may not be
All processes specified within the single shell command line will be
executed on the single machine matched with the job. Condor will not
distribute multiple processes of a command line pipe across multiple
condor_run will use the shell specified in the SHELLenvironment
variable, if one exists. Otherwise, it will use /bin/sh to execute the
By default, condor_run expects Perl to be installed in /usr/bin/perl.
If Perl is installed in another path, ask the Condor administrator to
edit the path in the condor_run script, or explicitly call Perl from
the command line:
% perl path-to-condor/bin/condor_run "shell-cmd"
condor_run exits with a status value of 0 (zero) upon complete success.
The exit status of condor_run will be non-zero upon failure. The exit
status in the case of a single error due to a system call will be the
error number (errno) of the failed call.
Condor Team, University of Wisconsin-Madison
Copyright (C) 1990-2009 Condor Team, Computer Sciences Department,
University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
Licensed under the Apache License, Version 2.0.
See the Condor Version 7.2.4 Manual or
http://www.condorproject.org/licensefor additional notices. condor-