CONDOR_TRANSFER_DATA(1)

✨ condor_transfer_data — the HTCondor Manual glow-up 💅

okay bestie, gather round, because condor_transfer_data is literally the little errand-runner of the HTCondor world and I am obsessed with her. She moves your spooled data for jobs you submitted with the -spool option. that's the whole vibe. let's get into it 🫶

---

🌸 SYNOPSIS 🌸

condor_transfer_data [-help | -version]

condor_transfer_data [-pool hostname[:portnumber] | -name scheddname |
-addr "<a.b.c.d:port>"] [cluster... | cluster.proc... | user... |
-constraint expression | -all]

---

💖 DESCRIPTION 💖

so condor_transfer_data tells HTCondor to go transfer your spooled data. it's designed to be the bestie of the -spool option over on condor_submit, like so:

$ condor_submit -spool mysubmitfile

when you submit a job with that -spool option, HTCondor spools all the input files, the job event log, and any proxy across a connection to the machine where the condor_schedd daemon is running. slay. and once those files are spooled? the machine you submitted from can literally disconnect from the network or go ahead and modify its local copies of the spooled files. main character energy, no strings attached ✨

then, when the job finishes, the job has JobStatus = 4, which means the job has completed. the output of the job gets spooled, and condor_transfer_data is the one who goes and retrieves the output of that completed job. she's giving ✨fetch✨.

---

👑 OPTIONS 👑

• -help — display usage information. a little "here's how I work" moment.
• -version — display version information.
• -pool hostname[:portnumber] — specify a pool by handing over the central manager's host name plus an optional port number.
• -name scheddname — send the command to a machine identified by scheddname.
• -addr "<a.b.c.d:port>" — send the command to a machine located at "<a.b.c.d:port>".
• cluster — transfer spooled data belonging to the specified cluster.
• cluster.proc — transfer spooled data belonging to a specific job in the cluster.
• user — transfer spooled data belonging to the specified user.
• -constraint expression — transfer spooled data for jobs which match the job ClassAd expression constraint.
• -all — transfer all spooled data. every last crumb. 💀

---

🌈 EXAMPLES 🌈

transfer output for all jobs in cluster 123:

$ condor_transfer_data 123

transfer output for a specific job:

$ condor_transfer_data 123.4

transfer output for all jobs belonging to user alice:

$ condor_transfer_data alice

transfer output for all completed spooled jobs:

$ condor_transfer_data -all

see? easy. iconic. periodt.

---

⭐ EXIT STATUS ⭐

• 0 — success 🎉
• 1 — failure 😭

---

🦋 SEE ALSO 🦋

condor_submit, condor_q, condor_tail

---

🌸 AVAILABILITY 🌸

Linux, MacOS, Windows

---

💜 AUTHOR 💜

HTCondor Team

---

🎀 COPYRIGHT 🎀

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.

---

and that's the whole page, bestie! this was CONDOR_TRANSFER_DATA(1) from the HTCondor Manual, dated Oct 16, 2026. go forth and transfer that data 💅💖✨