Re: [HTCondor-users] cgroup job scope

[Greg Thain <gthain@xxxxxxxxxxx>]

On 11/24/25 08:12, Thomas Hartmann wrote:
> Hi all,
>
> quick question but is the scope for job cgroups intended for users to 
> be used or primarily for condor to bookkeeping?


The scope is intended to for users. There is a cgroup(v2) rule the 
kernel tries to enforce -- that processes can only live in the leaf node 
of the cgroup hierarchy. Following the systemd convention, htcondor 
puts the processes of a job in a cgroup whose name ends in the string 
".slice". Because of this rule, if a job wants to create a sub-cgroup, 
it can't just make a sub-directory of the .slice cgroup it was born in. 
To allow jobs to further constrain their resource usage, the job's 
.slice cgroup has a parent cgroup named .scope which has no processes 
directly in it. The intention is that jobs can create subdirectories of 
the .scope cgroup. HTCondor reports memory and cpu usage from the 
.scope on down.


-greg