Jump to letter: [
CHMOPS
]
condor-ep - Configuration for an Execution Point
- Description:
This example configuration is good for installing an Execution Point.
After installation, one could join a pool or start an annex.
Packages
| condor-ep-23.10.18-1.el9.aarch64
[26 KiB] |
Changelog
by Tim Theisen (2024-11-19):
- Fix issue where an unresponsive libvirtd blocked an EP from starting up
|
| condor-ep-23.10.2-1.el9.aarch64
[26 KiB] |
Changelog
by Tim Theisen (2024-10-30):
- Fix for output file transfer errors obscuring input file transfer errors
|
| condor-ep-23.10.1-1.el9.aarch64
[27 KiB] |
Changelog
by Tim Theisen (2024-10-03):
- Improvements to disk usage enforcement when using LVM
- Can encrypt job sandboxes when using LVM
- More precise tracking of disk usage when using LVM
- Reduced disk usage tracking overhead
- Improvements tracking CPU and memory usage with cgroup v2 (on EL9)
- Don't count kernel cache pages against job's memory usage
- Avoid rare inclusion of previous job's CPU and peak memory usage
- HTCondor now re-checks DNS before re-connecting to a collector
- HTCondor now writes out per job epoch history
- HTCondor can encrypt network connections without requiring authentication
- htcondor CLI can now show status for local server, AP, and CM
- htcondor CLI can now display OAUTH2 credentials
- Uses job's sandbox to convert image format for Singularity/Apptainer
- Bug fix to not lose GPUs in Docker job on systemd reconfig
- Bug fix for PID namespaces and condor_ssh_to_job on EL9
|