CONDOR_DAGMAN(1)

📦
version 25.14.1 · 12 versions
, in fedora 43

💖 condor_dagman — HTCondor Manual 💖

okay so bestie, welcome to condor_dagman, aka the node scheduler for automating HTCondor job workflows. she's the one who runs the show behind the scenes, and you're probably not supposed to talk to her directly, but here we are, and honestly? iconic. 🎀

✨ NAME ✨

condor_dagman — HTCondor Manual

Node scheduler for automating HTCondor job workflows. 🦋

🌸 SYNOPSIS 🌸

condor_dagman [-help | -version]

condor_dagman -p 0 -f -l . [OPTIONS] DAG_file [DAG_file...]

condor_dagman -p 0 -f -l . [-WaitForDebug] [-CsdVersion VersionString]
[-AllowVersionMismatch] [-Batch-Name name] [-Dag DAG_file] [-Debug
level] [-Dot] [-DryRun] [-Lockfile filename] [-Priority priority]
[-SubmitMethod value] [-UseDagDir] [-AlwaysRunPost | -DontAlwaysRunPost]
[-suppress_notification | -dont_suppress_notification] [-AutoRescue
<0|1>] [-DoRescueFrom N] [-DoRecovery] [-RescueFile filename]
[-load_save filename] [-MaxHold N] [-MaxIdle N] [-MaxJobs N] [-MaxPost
N] [-MaxPre N]

💅 DESCRIPTION 💅

so basically she's a meta node scheduler that automatically manages HTCondor user workflows, and those workflows describe jobs as nodes in a Directed Acyclic Graph (DAG). and the way every single part of that DAG — nodes, dependencies, visualizations, all of it — gets described in a DAG Description File (*.dag) using the DAG Description Language (DDL)?? obsessed. 👑

✨ OPTIONS ✨

  • -help — she'll show you how to use her. usage info, that's it, that's the post.
  • -version — tells you what version she is. her whole identity, honestly.
  • -WaitForDebug — pauses DAGMan's execution until a debugger is attached. lowkey in her waiting era. 🫶
NOTE: Requires manual setting of wait_for_debug variable to false to continue execution. not me having to flip my own switch 😭
  • -CsdVersion VersionString — the version of condor_submit_dag that produced the scheduler universe job representing this DAGMan instance. receipts, basically.
  • -AllowVersionMismatch — allows a version difference between condor_dagman herself and the *.condor.sub file that condor_submit_dag produced.
WARNING: ⚠️ This option should only be used if absolutely necessary, because version mismatches can cause subtle problems when running DAGMan. subtweeting yourself is never the move, bestie.
  • -Batch-Name name — sets the JobBatchName to name for all jobs that condor_dagman places to the AP.
  • -dag DAG_file — name a file that details a DAG structure for condor_dagman to manage. (yes the SYNOPSIS up there spells it -Dag and the option list spells it -dag — she contains multitudes, don't come for her 💀)
  • -Debug level — sets the debug log level. scroll down for the level lore, see below.
  • -Dot — exits immediately after producing the first DAG visual DOT file. she said "made the art, now I'm leaving" 🎨
  • -DryRun — tells condor_dagman to execute the DAG without actually placing any jobs to the AP. window shopping era.
  • -Lockfile filename — path to a file to write condor_dagman process information. this prevents other condor_dagman processes executing the same DAG(s) from being executed in the same directory. it's giving "this is my room, get out" 🙈
  • -Priority priority — sets the minimum JobPrio for jobs managed by condor_dagman.
  • -SubmitMethod value — specifies how condor_dagman will place managed jobs to the AP. values below, bestie.
  • -UseDagDir — tells condor_dagman to execute each specified DAG from their respective directories. everyone sticks to their own lane ✨
  • -AlwaysRunPost — always execute POST scripts, even upon failure of any PRE scripts.
  • -DontAlwaysRunPost — only execute POST scripts after a node's list of jobs have completed (Success or Failure). Default.
  • -suppress_notification — suppresses email notifications for all managed jobs. inbox zero queen 🎀
  • -dont_suppress_notification — allows email notifications for any managed jobs that have notifications specified. Default.
  • -AutoRescue <0|1> — automatically detects rescue DAG files upon startup and rescues from the most recent (highest number) rescue file discovered. 0 is False. Default 1 is True.
  • -DoRescueFrom N — specifies a specific rescue number to locate and restore state from. pick your fighter 🔥
  • -RescueFile filename — specifies a specific rescue file by name to restore state from.
  • -DoRecovery — specifies to startup in recovery mode (restore state from *.nodes.log). we're healing 💜
  • -load_save filename — specifies a specific SAVE_POINT_FILE to restore state from.
  • -MaxIdle N — sets the maximum number of idle jobs allowed before placing more jobs to the AP. if not specified, then this is set to the value of DAGMAN_MAX_JOBS_IDLE.
NOTE: condor_dagman can place jobs beyond this threshold in a single job placement cycle, but won't place more jobs until the detected number of idle jobs drops below the specified threshold again. so like, she overshoots once and then chills. 💅
  • -MaxJobs N — sets the maximum number of nodes that have placed a list of jobs to the AP at any given moment. if not specified, then this is set to the value of DAGMAN_MAX_JOBS_SUBMITTED.
  • -MaxPre N — sets the maximum number of PRE scripts being executed at any given moment. if not specified, then this value is set to DAGMAN_MAX_PRE_SCRIPTS.
  • -MaxPost N — sets the maximum number of POST scripts being executed at any given moment. if not specified, then this value is set to DAGMAN_MAX_POST_SCRIPTS.
  • -MaxHold N — sets the maximum number of HOLD scripts being executed at any given moment. if not specified, then this value is set to DAGMAN_MAX_HOLD_SCRIPTS.

🌈 GENERAL REMARKS 🌈

condor_dagman is not intended to be ran manually unless it's to debug or test DAGMan for a specific reason. like, she has people for this. instead, to execute a DAG, place a meta scheduler universe job to the local AP via condor_submit_dag or htcondor. periodt. 💅

the following options that appear first are for DaemonCore:

  • -p 0 : causes DAGMan to run without a Socket.
  • -f : run in foreground (i.e. not spawned by condor_master).
  • -l . : sets the debug log directory to the execution directory.

the following options from condor_submit_dag can also be provided to condor_dagman, and they will be used for submitting SUBDAG's:

  • -dagman
  • -f / -force
  • -import_env
  • -include_env Var1[,Var2...]
  • -insert_env key=value[,key=value...]
  • -notification
  • -outfile_dir
  • -update_submit
  • -v / -verbose

🦋 Debug Level Values 🦋

okay so the vibe check on debug levels, bestie:

  • 0 — Never produce output except for usage info.
  • 1 — Very quiet. Only output severe errors.
  • 2 — Normal output and error messages
  • 3 — (Default) Print warnings.
  • 4 — Internal debugging output.
  • 5 — Outer loop debugging.
  • 6 — Inner loop debugging.
  • 7 — Output parsed DAG input lines.

💜 Submit Method Values 💜

  • 0 — Run condor_submit
  • 1 — Direct place job(s) to local condor_schedd

⭐ EXIT STATUS ⭐

  • 0 — Success 🥳
  • 1 — Failure has occurred 😭
  • 2 — DAGMan aborted
  • 3 — DAGMan restart

🔥 EXAMPLES 🔥

Display installed condor_dagman version:

$ condor_dagman -version

Display condor_dagman usage:

$ condor_dagman -help

Manually run sample.dag:

$ condor_dagman -p 0 -f -l . sample.dag

Execute condor_dagman in a debugger:

$ condor_dagman -p 0 -f -l . -waitfordebug -dag sample.dag

👀 SEE ALSO 👀

  • condor_submit_dag

🌍 AVAILABILITY 🌍

Linux, MacOS, Windows. she said cross-platform, no cap. 🌈

💖 AUTHOR 💖

HTCondor Team

1990-2026, Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0.

okay bestie that's the whole page!! 💖✨🦋🌸💅🫶

this absolute masterclass of a manual page is brought to you by the HTCondor Manual, dated Oct 16, 2026, and it lives at CONDOR_DAGMAN(1). go run a DAG. slay. 👑

📦 where this page comes from