CONDOR_REMOTE_CLUSTER(1)

✨ CONDOR_REMOTE_CLUSTER ✨ (that's section 1 of the HTCondor Manual, bestie)

aka condor_remote_cluster β€” the little command that manages and configures the clusters you wanna reach 🫢


🌸 NAME 🌸

condor_remote_cluster β€” HTCondor Manual. It manages and configures the clusters that are gonna be accessed. That's the whole job. Iconic, honestly.


🌈 SYNOPSIS 🌈

condor_remote_cluster [-h || --help]

condor_remote_cluster [-l || --list] [-a || --add <host> [schedd]] [-r
|| --remove <host>] [-s || --status <host>] [-t || --test <host>]

πŸ’– DESCRIPTION πŸ’–

okay so condor_remote_cluster is part of a whole feature that lets you access high throughput computing resources from your local desktop using only an SSH connection. no extra nonsense. just SSH. periodt. πŸ’…

condor_remote_cluster handles the management and configuration of the access point of that remote computing resource. Once the initial setup is done, you can submit jobs to your local job queue, and those jobs get forwarded over to the remote system. the way that works?? lowkey magical. ✨

oh and a <host> is written like this:

[user@]fqdn.example.com[:22]

so user@ is optional, the port is optional, and it's giving very flexible. 😌


πŸŽ€ OPTIONS πŸŽ€

  • -help β€” Print usage information and exit. quick lil "how do I even" button, then it dips. πŸ“–
  • -list β€” List all installed clusters. every single one, right there in your terminal. ⭐
  • -remove <host> β€” Remove an already installed cluster, where the cluster is identified by <host>. gone. bye bestie. πŸ‘‹
  • -add <host> [scheduler] β€” Install and add a cluster defined by <host>. The optional scheduler specifies the scheduler on the cluster. Valid values are pbs, lsf, condor, sge or slurm. If not given, the default will be pbs. so if you don't pick, pbs is the main character by default πŸ”₯
  • -status <host> β€” Query and print the status of an already installed cluster, where the cluster is identified by <host>. vibe check for your cluster, basically πŸ¦‹
  • -test <host> β€” Attempt to submit a test job to an already installed cluster, where the cluster is identified by <host>. yes it actually tries. yes that's the point. πŸ’€

πŸ‘‘ 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.


ok that's the whole page, no cap. this came straight out of the HTCondor Manual πŸ’–

and this lil cutie was dated Oct 16, 2026 β€” that's the version/date energy for CONDOR_REMOTE_CLUSTER(1), slay 🌸✨

πŸ“¦ where this page comes from