> I don't know if su works differently when using systemd and not sysvinit> and makes this problem appear only when using systemd.Ok, I don't see that behavior here (I'm not using systemd as init system but I
have it installed), start-stop-daemon and /bin/su use the setuid syscall,
but su uses pam, so, its related to the pam-session part. I still don't
understand why is it different if you are using a systemd init system or not.