Hi everyone! Recently there's a trend for session-specific processes and services (and even GUI apps, via `systemd-run --scope') to run as their own user units on eligible systems/distros, to have a clean and controlled cgroup hierarchy. I've been looking at https://systemd.io/DESKTOP_ENVIRONMENTS/ and see no answer to the following question: how can a process, e. g. gvfs-daemon, know which logind-session is it run for (for example, to find out the seat by session ID), if it's actually in a user service unit? The libsystemd source for sd_pid_get_session(), which is used by gvfs as of today, gives a hint that function won't work in that case, since a user service process's /proc/self/cgroup does not contain "session-XXX.scope".
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
