Package: condor Version: 25.7.2+dfsg-1 Architecture: amd64 Maintainer: Debian HPC Team Installed-Size: 32936 Depends: adduser, libdate-manip-perl, python3, python3-cryptography, python3-requests, libcom-err2, libgssapi-krb5-2, libk5crypto3, libkrb5-3, libkrb5support0, libmunge2, net-tools, cryptsetup, libjs-bootstrap, libjs-jquery, jq, libscitokens0t64, libssl3t64 (>= 3.0.0), libvomsapi1t64, perl:any, python3:any, libc6 (>= 2.38), libcurl4t64 (>= 7.16.2), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.0), libgomp1 (>= 4.9), libpcre2-8-0 (>= 10.22), libsqlite3-0 (>= 3.5.9), libstdc++6 (>= 14), libuuid1 (>= 2.16) Recommends: bash-completion, openssh-server Suggests: docker.io, coop-computing-tools, singularity-container, slurm-client Conflicts: condor-upgrade-checks, htcondor Breaks: condor-upgrade-checks, htcondor Replaces: condor-upgrade-checks, htcondor Section: science Priority: optional Homepage: https://htcondor.org/ Description: distributed workload management system Like other full-featured batch systems, HTCondor provides a job queueing mechanism, scheduling policy, priority scheme, resource monitoring, and resource management. Users submit their serial or parallel jobs to HTCondor; HTCondor places them into a queue. It chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. . Unlike more traditional batch queueing systems, HTCondor can also effectively harness wasted CPU power from otherwise idle desktop workstations. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user. . This package can set up an appropriate initial configuration at install time for a machine intended either as a member of an existing HTCondor pool or as a "Personal" (single machine) HTCondor pool.