CONDOR_SUSPEND(1)

📦
version 25.14.1 · 12 versions
, in fedora 43

💅 NAME 💅

ok so condor_suspend — it's from the HTCondor Manual bestie, and what it does is suspend running job(s) from HTCondor. that's it. that's the whole vibe. pausing ur lil jobs, putting them in time-out (affectionately). 🫶

✨ SYNOPSIS ✨

condor_suspend [-help | -version]

condor_suspend [OPTIONS] [cluster... | cluster.proc... | user...]

condor_suspend [-debug] [-long] [-totals] [-all] [-constraint
expression] [-pool hostname[:portnumber] | -name scheddname | -addr
"<a.b.c.d:port>"]

🌸 DESCRIPTION 🌸

okay so here's the tea: when you suspend a job, all the processes in that job get sent the SIGSTOP signal, or the equivalent of it. so they stop doing stuff. no cap.

the consequences, in bullet-adjacent spirit but honestly just let me yap:

  • they consume no cpu usage 🎀
  • but they continue to use memory and scratch disk space (the freeloaders 😭)
  • suspended jobs still consume the slot they run in — the slot does NOT get freed, sorry bestie
  • and they're still charged to submitters in term of user priority

so like. it's a pause, not a cancellation. the job is still there, still eating ur resources, just not actively computing. it's giving "napping in the group chat."

lowkey important: for any given job, only the owner of the job or one of the queue super users (defined by the QUEUE_SUPER_USERS macro) can suspend the job. so if it's not ur job and ur not a super user? not ur moment. 🙈

👑 OPTIONS 👑

  • -help — shows u the usage information. the "how do i work this thing" button.
  • -version — shows u the version information. bc knowing what version ur running is lowkey self care.
  • -long — displays the result ClassAd. full detail mode, no crumbs.
  • -totals — displays the success/failure totals. the scoreboard energy.
  • -pool hostname[:portnumber] — pick a pool by handing over the central manager's host name and an optional port number.
  • -name scheddname — sends the command to a machine identified by scheddname.
  • -addr "<a.b.c.d:port>" — sends the command to a machine located at "<a.b.c.d:port>".
  • -debug — causes debugging information to be sent to stderr, based on the value of the configuration variable TOOL_DEBUG. it's gonna be chatty. 🗣️
  • -constraint expression — suspend all jobs which match the job ClassAd expression constraint. filtering? iconic.
  • -all — suspend all the jobs in the queue. every single one. absolutely everyone. 💀
  • cluster — suspend all jobs in the specified cluster.
  • cluster.process — suspend the specific job in the cluster.
  • user — suspend jobs belonging to specified user.

🌈 GENERAL REMARKS 🌈

ok now the important little details, pls read these fr fr:

  • if the -name option is specified, the named condor_schedd is targeted for processing. otherwise, the local condor_schedd is targeted.
  • when a job is suspended, the match between the condor_schedd and machine is not been broken, such that the claim is still valid. (yes we're keeping that wording, it's part of the lore ✨)
  • an administrator might want to suspend the jobs in a pool to quickly reduce the power draw in a pool, in the case where they may be able to condor_continue the jobs after a short while, and do not wish the jobs to be vacated and then restart from their beginning or last checkpoint. like, why restart the whole thing when u can just... pause it? exactly. main character energy.
  • use condor_continue to continue suspended job executions. the un-pause. the resume. the "okay wake up babe." ⭐

🎀 EXIT STATUS 🎀

  • 0 — Success ✅
  • 1 — Failure has occurred 😭

🦋 EXAMPLES 🦋

to suspend a specific job:

$ condor_continue 432.1

to suspend all jobs except for a specific user:

# condor_suspend -constraint 'Owner =!= "foo"'
(yes, the first example says condor_continue. we are reproducing it character for character, bc the facts don't change even when the vibe does. iykyk 😌)

🔥 SEE ALSO 🔥

condor_continue, condor_rm, condor_hold, condor_release, condor_vacate_job, condor_vacate

💖 AVAILABILITY 💖

Linux, MacOS, Windows — so basically everyone's invited to the function 🫶

⭐ AUTHOR ⭐

HTCondor Team — the legends themselves, we stan.

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. legal says slay, and honestly, they ate. 👑

and that's the whole page bestie!! this was CONDOR_SUSPEND(1) from the HTCondor Manual, and if u ever forget when this version dropped: it's dated Oct 16, 2026. periodt. 💅✨

📦 where this page comes from