Hi all,quick question - but in principle the condor job cgroup hierarchy lives outside of the systemd managed slices, or?
I have tried to force the job cgroup slice underneath the condor.service, but have not managed to get them into a clean(??) hierarchy as such (where the condor.service lives in the system.slice of systemd)
i.e., I had tried to tinker with the condor base cgroup [1] and maybe get the daemons in a dedicated slice with ensured resources and the jobs underneaths in the hierarchy with their resources managed by Condor (and relative to their parent). However, I am not sure, if/how I can actually manage to get the job slice, spawned by Condor, to be rooted under the service slice for condor spawned by systemd. I.e., like a drop-in for the condor.service with a dedicated `[Slice]` section - and than tune BASE_CGROUP accordingly?
Maybe somebody has already adjusted their hierarchy in a similar manner and got it working?
Cheers, Thomas [1] [root@batch1313 ~]# condor_config_val BASE_CGROUP condordesy.service/condorjob.slice [root@batch1313 ~]# cat /proc/748707/cgroup 0::/system.slice/condordesy.service/condorjob.slice/_var_lib_condor_execute_slot1_28@xxxxxxxxxxxxxxxxxxxxxxx/_var_lib_condor_execute_slot1_28@xxxxxxxxxxxxxxxxxxxxxxx [2] [root@batch1313 ~]# systemctl show condor.service -p Slice Slice=system.slice
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature