GET_HTCONDOR(1)
π GET_HTCONDOR(1) π
okay bestie, so this is the get_htcondor page from the HTCondor Manual β the manual is literally right there in the title, iconic β and it's about installing and configuring HTCondor on Linux machines. that's the whole vibe. let's go β¨
πΈ NAME πΈ
get_htcondor β HTCondor Manual
Install and configure HTCondor on Linux machines. yes that's it, that's the job π«Ά
β¨ SYNOPSIS β¨
get_htcondor <-h | --help>
get_htcondor [--[no-]dry-run] [--channel name] [--minicondor |
[--central-manager | --submit | --execute] central-manager-name]
[--shared-filesystem-domain filesystem-domain-name]
get_htcondor --dist
π¦ DESCRIPTION π¦
this tool installs and configures HTCondor on Linux machines, no cap. for the full detailed instructions go peek at https://htcondor.readthedocs.io/en/latest/getting-htcondor π
but this page? this page is the quick reference, bestie β just the options, right to the point. it also has a whole section about why it installs the configurations it installs, because the reasonings are lowkey the interesting part.
π OPTIONS π
-helpβ prints a lil usage reminder, so you remember what you were doing π--dry-runβ does NOT actually issue any commands, it just prints them out so you can see them. [default] β yes babe, it's shy by default π--no-dry-runβ okay NOW we're doing it: issues all the commands needed to actually install HTCondor. committing to the bit β¨--channelname β specify the channel name to install from. name can becurrent, which is the most recent release with new features [default], orstable, which is the most recent release with only bug-fixes π--distβ display the detected operating system and then dip. bye π--minicondorβ configure this as a single-machine ("mini") HTCondor. [default] β just you, your machine, no network drama π«Ά--central-managercentral-manager-name β--submitcentral-manager-name β--executecentral-manager-name β configure this installation with the central manager, submit, or execute role. pick your main character arc π--shared-filesystem-domainfilesystem-domain-name β configure this installation to assume that machines specifying the same filesystem-domain-name share a filesystem. they're all besties, they share π
π EXIT STATUS π
- on success, it exits with code
0β slay β¨ - failures detected by
get_htcondorwill result in exit code1β not slay π - other failures may have other exit codes. sometimes things just happen, and it's not this tool's fault, fr fr
π INSTALLED CONFIGURATION π
so this tool may install four different configurations π we're gonna talk about the single-machine one first, and then the three parts of the multi-machine configuration all together as a group, because they're a package deal.
our goal here is to document the reasoning behind all the little details β because (a) the details can totally obscure that reasoning, and (b) the details are gonna change as we keep improving HTCondor. so like, don't get too attached to specifics, bestie.
as a general note: the configurations this tool installs make extensive use of metaknobs β these are lines in HTCondor configuration files that look likeuse x : y. to determine exactly what configuration a metaknob sets, runcondor_config_val use x:y. iykyk π
π§ Single-Machine Installation π§
the single-machine installation performed by get_htcondor uses the minicondor package. (a "mini" HTCondor is a single-machine HTCondor system installed with administrative privileges, okay? that's what mini means here.)
because the different roles in the HTCondor system are all on the same machine, we configure all network communications to occur over the loopback device, where we don't have to worry about eavesdropping or requiring encryption. nobody's peeking, nobody's snooping π
we use the FS method, which depends on the local filesytem, to identify which user is attempting to connect, and we restrict access correspondingly.
the get_htcondor tool installs the standard minicondor package from the HTCondor repositories. see the file it creates, /etc/condor/config.d/00-minicondor, for details. literally go read it πΈ
π Multi-Machine Installation π
because the three roles must communicate over the network to form a complete pool in this case,, security is a much bigger concern π so we therefore require authentication and encryption on every single connection. no exceptions, periodt.
thankfully, almost all of the network communication is daemon-to-daemon, so we don't have to burden individual users with that aspect of security. instead, users submit jobs on the submit-role machine, using FS to authenticate. users may also need to contact the central manager (when running condor_status, for example), but they never need to write anything to it β so we've configured authentication for read-only commands to be optional. letting the girlies look π
daemon-to-daemon communication is authenticated with the IDTOKENS method. (if a user needs to submit jobs remotely, they can also use the IDTOKENS method, it's just more work; see condor_token_fetch.) each role installed by this tool has a copy of the password, which is used to generate an IDTOKEN, which is used for all daemon-to-daemon authentication. both the password and the IDTOKEN can only be read by privileged processes. an IDTOKEN can only be validated by the holder of the corresponding password, so each daemon in the pool has to have both. it takes two, bestie π
this tool installs the role-specific configuration in the files:
/etc/condor/config.d/01-central-manager.config/etc/condor/config.d/01-submit.config/etc/condor/config.d/01-execute.config
consult them for details! π
π 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.
okay so that's the whole page fr fr π«Ά and bestie, before you go β this one was HTCondor Manual source, version Oct 16, 2026. that's the date on the tin, so if you're citing it, that's your girl π β¨ ily, go install something ππ¦
π¦ where this page comes from
- fedora 43: condor 25.14.1-1.fc43 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms