Michal Koutný

I don't think this is bug in flatpak or systemd per se. It's rather an unclear migration model of foreign tasks on the unified hierarchy. I've raised it in [cgroup...

@Steiniche Unfortunately, the upstream tracker is usually used for two most recently released major systemd versions. ``` git log --no-merges --oneline v239..v251 src/core/cgroup.c src/shared/cgroup-setup.c | wc -l 221 ``` (I...

Hello. What does the following say on your system: ``` grep -E "cpuset|cgroup2" /proc/mounts cat /sys/fs/cgroup/cgroup.controllers # edit: or wherever your cgroup2 tree is moutned ``` ? Also, what systemd...

Thanks. So the cpuset controller is bound to the v2 hierarchy and it also shows that systemd runs in the unified mode (that was perhaps the critical change between updates)....

@Hubro With the recent systemd version you should be able to specify `AllowedCPUs=` directive. You can't set it directly on root (`-.slice`) but all 1st level children instead (`init.scope`, `system.slice`...

Setting the cgroup attributes should work at runtime exactly as you did (alternatively you can edit slice unit or drop-in files and call `systemctl daemon-reload`), restart of slices is not...

> 3. With the introduction of SystemD in SUSE products I heard horror stories about how SystemD freezes when external programs manipulate its group setting. It was LTP at that...

> But trying to update every systemd unit to exclude them from executing on those CPUs would not be trivial. Actually, you should just be able to leverage the hierarchy...

The setup code and program proper share the same file descriptors (namely stdout), so I don't see an obvious way how to split their outputs. However, the reported message could...

Cross-link to a popular demand, #39.