Mission Control is D-Bus-activated. Under "systemd --user", this results in it being part of the dbus.service cgroup: it is part of dbus for the purposes of things like resource control. With dbus-daemon 1.10 configured with --enable-user-session, we can do better: a systemd user service will result in it being placed in its own cgroup. This also allows avoiding Bug #53220 without resorting to the mc-wait-for-name tool.
Created attachment 118442 [details] [review] Add a systemd user service corresponding to the D-Bus session service This lets Mission Control run in its own cgroup. As a bonus, systemd activation doesn't have to resort to hacks like mc-wait-for-name, because systemd understands the concept of a systemd service that maps to multiple D-Bus service names, and will only start it once. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=92115
Created attachment 118443 [details] [review] [Gabble] Add a systemd user service This puts telepathy-gabble in its own cgroup, instead of being a child process of dbus-daemon in the dbus.service cgroup. --- The equivalent for telepathy-gabble. I'm not going to go round all the other CMs doing the same, but another contributor could, if someone wants to.
Are there any plans to merge this? (and to add the systemd .service files for the other CM?)
Created attachment 128348 [details] [review] [TPL] Add a systemd user service
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-mission-control/issues/83.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.