runguard.c has the default location hardcoded and no one complained. It would be (relatively easy) to use the autoconf option (and would have taken less code changes).
I found this when I tried to move the mounted cgroup locations to another dir to setup cgroupv2 in a unified structure. I'm fine with keeping the behaviour if we have a good reason for it but a quick websearch shows that everyone uses /sys/fs/cgroup.
runguard.c has the default location hardcoded and no one complained. It would be (relatively easy) to use the autoconf option (and would have taken less code changes).
I found this when I tried to move the mounted cgroup locations to another dir to setup cgroupv2 in a unified structure. I'm fine with keeping the behaviour if we have a good reason for it but a quick websearch shows that everyone uses
/sys/fs/cgroup.