Description of problem: When sudo'ing, su'ing or calling "runuser -l", pam_systemd makes the cgroup change, but not always, e.g: - it changes the cgroup when sudo'ing from a service - it doesn't change the cgroup when sudo'ing from another user session Why is this done? What is the benefit for doing this? IMHO if we are in a service already, nothing should happen at all and the executable called after sudo'ing or su'ing should remain in the cgroup of the service. This would would greatly permit reusing customer's legacy scripts that internally make use of "su" or "sudo" without rewriting anything. Version-Release number of selected component (if applicable): systemd-219+ How reproducible: Always