Linux Certif

Toute la documentation sur la certification Linux LPI

condor_submit_dag

Name

condor_submit_dag Manage and queue jobs within a specified DAG for execution on remote machines

Synopsis

condor_submit_dag [ -help | -version ] condor_submit_dag [ -no_submit ] [ -verbose ] [ -force ] [ -maxidle NumberOfJobs ] [ -maxjobs NumberOfJobs ] [ -dagman DagmanExecutable ] [ -maxpre NumberOfPREscripts ] [ -maxpost NumberOfPOSTscripts ] [ -notification value ] [ -noeventchecks ] [ -allowlogerror ] [ -r schedd_name ] [ -debug level ] [ -usedagdir ] [ -outfile_dir directory ] [ -config ConfigFileName ] [ -insert_sub_file FileName ] [ -append Command ] [ -oldrescue 0|1 ] [ -autorescue 0|1 ] [ -dorescuefrom number ] [ -allowversionmismatch ] [ -no_recurse ] [ -update_submit ] [ -import_env ] [ -DumpRescue ] [ -valgrind ] DAGInputFile1 [ DAGInputFile2 ... DAGInputFileN ]

Description

condor_submit_dag is the program for submitting a DAG (directed acyclic graph) of jobs for execution under Condor. The program enforces the job dependencies defined in one or more DAGInputFile s. Each DAGInputFile contains commands to direct the submission of jobs implied by the nodes of a DAG to Condor. See the Condor User Manual, section for a complete description.

Options

-help

Display usage information.

-version

Display version information.

-no_submit

Produce the Condor submit description file for DAGMan, but do not submit DAGMan as a Condor job.

-verbose

Cause condor_submit_dag to give verbose error messages.

-force

Require condor_submit_dag to overwrite the files that it produces, if the files already exist. Note that dagman.outwill be appended to, not overwritten. If new-style rescue DAG mode is in effect, and any new-style rescue DAGs exist, the -force flag will cause them to be renamed, and the original DAG will be run. If old-style rescue DAG mode is in effect, any existing old-style rescue DAGs will be deleted, and the original DAG will be run. Section details rescue DAGs.

-maxidle NumberOfJobs

Sets the maximum number of idle jobs allowed before condor_dagman stops submitting more jobs. Once idle jobs start to run, condor_dagman will resume submitting jobs. NumberOfJobs is a positive integer. If the option is omitted, the number of idle jobs is unlimited. Note that for this argument, each individual process within a cluster counts as a job, which is inconsistent with -maxjobs .

-maxjobs NumberOfJobs

Sets the maximum number of jobs within the DAG that will be submitted to Condor at one time. NumberOfJobs is a positive integer. If the option is omitted, the default number of jobs is unlimited. Note that for this argument, each cluster counts as one job, no matter how many individual processes are in the cluster.

-dagman DagmanExecutable

Allows the specification of an alternate condor_dagman executable to be used instead of the one found in the user's path. This must be a fully qualified path.

-maxpre NumberOfPREscripts

Sets the maximum number of PRE scripts within the DAG that may be running at one time. NumberOfPREScripts is a positive integer. If this option is omitted, the default number of PRE scripts is unlimited.

-maxpost NumberOfPOSTscripts

Sets the maximum number of POST scripts within the DAG that may be running at one time. NumberOfPOSTScripts is a positive integer. If this option is omitted, the default number of POST scripts is unlimited.

-notification value

Sets the e-mail notification for DAGMan itself. This information will be used within the Condor submit description file for DAGMan. This file is produced by condor_submit_dag . See notification within the section of submit description file commands in the condor_submit manual page on page for specification of value .

-noeventchecks

This argument is no longer used; it is now ignored. Its functionality is now implemented by the DAGMAN_ALLOW_EVENTSconfiguration macro (see section ).

-allowlogerror

This optional argument has condor_dagman try to run the specified DAG, even in the case of detected errors in the user log specification. As of version 7.3.2, this argument has an effect only on DAGs containing Stork job nodes.

-r schedd_name

Submit condor_dagman to a remote machine, specifically the condor_schedd daemon on that machine. The condor_dagman job will not run on the local condor_schedd (the submit machine), but on the specified one. This is implemented using the -remote option to condor_submit . Note that this option does not currently specify input files for condor_dagman , nor the individual nodes to be taken along! It is assumed that any necessary files will be present on the remote computer, possibly via a shared file system between the local computer and the remote computer. It is also necessary that the user has appropriate permissions to submit a job to the remote machine; the permissions are the same as those required to use condor_submit -remote option. If other options are desired, including transfer of other input files, consider using the -no_submit option, modifying the resulting submit file for specific needs, and then using condor_submit on that.

-debug level

Passes the the level of debugging output desired to condor_dagman . level is an integer, with values of 0-7 inclusive, where 7 is the most verbose output. A default value of 3 is passed to condor_dagman when not specified with this option. See the condor_dagman manual page on page for detailed descriptions of these values.

-usedagdir

This optional argument causes condor_dagman to run each specified DAG as if condor_submit_dag had been run in the directory containing that DAG file. This option is most useful when running multiple DAGs in a single condor_dagman . Note that the -usedagdir flag must not be used when running an old-style rescue DAG (see section ).

-outfile_dir directory

Specifies the directory in which the .dagman.outfile will be written. The directory may be specified relative to the current working directory as condor_submit_dag is executed, or specified with an absolute path. Without this option, the .dagman.outfile is placed in the same directory as the first DAG input file listed on the command line.

-config ConfigFileName

Specifies a configuration file to be used for this DAGMan run. Note that the options specified in the configuration file apply to all DAGs if multiple DAGs are specified. Further note that it is a fatal error if the configuration file specified by this option conflicts with a configuration file specified in any of the DAG files, if they specify one. For more information about how condor_dagman configuration files work, see section .

-insert_sub_file FileName

Specifies a file to insert into the .condor.subfile created by condor_submit_dag . The specified file must contain only legal submit file commands. Only one file can be inserted. (If both the DAGMAN_INSERT_SUB_FILE configuration variable and -insert_sub_file are specified, -insert_sub_file overrides DAGMAN_INSERT_SUB_FILE.) The specified file is inserted into the .condor.subfile before the Queue command and before any commands specified with the -append option.

-append Command

Specifies a command to append to the .condor.subfile created by condor_submit_dag . The specified command is appended to the .condor.subfile immediately before the Queue command. Multiple commands are specified by using the -append option multiple times. Each new command is given in a separate -append option. Commands with spaces in them must be enclosed in double quotes. Commands specified with the -append option are appended to the .condor.subfile after commands inserted from a file specified by the -insert_sub_file option or the DAGMAN_INSERT_SUB_FILE configuration variable, so the -append command(s) will override commands from the inserted file if the commands conflict.

-oldrescue 0|1

Whether to use "old-style" rescue DAG naming (see section ) when creating a rescue DAG (0 = false, 1 = true).

-autorescue 0|1

Whether to automatically run the newest rescue DAG for the given DAG file, if one exists (0 = false, 1 = true).

-dorescuefrom number

Forces condor_dagman to run the specified rescue DAG number for the given DAG. A value of 0 is the same as not specifying this option. Specifying a non-existent rescue DAG is a fatal error.

-allowversionmismatch

This optional argument causes condor_dagman to allow a version mismatch between condor_dagman itself and the .condor.subfile produced by condor_submit_dag (or, in other words, between condor_submit_dag and condor_dagman ). WARNING! This option should be used only if absolutely necessary. Allowing version mismatches can cause subtle problems when running DAGs. (Note that, starting with version 7.4.0, condor_dagman no longer requires an exact version match between itself and the .condor.subfile. Instead, a "minimum compatible version" is defined, and any .condor.subfile of that version or newer is accepted.)

-no_recurse

This optional argument causes condor_submit_dag to not run itself recursively on nested DAGs (the default is that recursion is enabled). (DAG nodes specified with the SUBDAG EXTERNALkeyword or with submit file names ending in .condor.subare considered nested DAGs, and, by default, condor_submit_dag -no_submit -update_submit is run on the corresponding DAG files.)

-update_submit

This optional argument causes an existing .condor.subfile to not be treated as an error; rather, the .condor.subfile will be overwritten, but the existing values of -maxjobs , -maxidle , -maxpre , and -maxpost will be preserved.

-import_env

This optional argument causes condor_submit_dag to import the current environment into the environment command of the .condor.subfile it generates.

-DumpRescue

This optional argument tells condor_dagman to immediately dump a rescue DAG and then exit, as opposed to actually running the DAG. (This feature is mainly intended for testing.)

-valgrind

This optional argument causes the submit description file generated for the submission of condor_dagman to be modified. The executable becomes valgrind run on condor_dagman , with a specific set of arguments intended for testing condor_dagman . Note that this argument is intended for testing purposes only. Using the -valgrind option without the necessary valgrind software installed will cause the DAG to fail. If the DAG does run, it will run much more slowly than usual.

See Also

Condor User Manual

Exit Status

condor_submit_dag will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

Examples

To run a single DAG:

% condor_submit_dag diamond.dag To run a DAG when it has already been run and the output files exist:

% condor_submit_dag -force diamond.dag To run a DAG, limiting the number of idle node jobs in the DAG to a maximum of five:

% condor_submit_dag -maxidle 5 diamond.dag To run a DAG, limiting the number of concurrent PRE scripts to 10 and the number of concurrent POST scripts to five:

% condor_submit_dag -maxpre 10 -maxpost 5 diamond.dag To run two DAGs, each of which is set up to run in its own directory:

% condor_submit_dag -usedagdir dag1/diamond1.dag dag2/diamond2.dag

Author

Condor Team, University of Wisconsin-Madison

Copyright

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.4.2 Manual or http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu