[arch-general] Why "systemd --user" process hanging around after logout?
I've noticed recently that even after I log out of my desktop env (XFCE) there is a process tree left hanging around running "systemd --user" under my user ID (with a bunch of gvfs child processes running under it). I wouldn't normally care about this, but if I then try to power down the machine, that running process seems to block syslog from successfully shutting down, and so the shutdown process waits for an extra minute and a half until it finally kills the process and powers off. If I manually kill the "systemd --user" process tree, I have no such issues and the machine can power down instantly. Anyone have an idea why this is happening / how to fix? Either by forcing "systemd --user" to terminate on logout, or by forcing syslog and/or the shutdown process to not be blocked by systemd? I did some digging on this, and saw some indication that setting "KillUserProcesses=yes" in /etc/systemd/logind.conf would force the systemd process to get shut down. But I tried changing that setting and it didn't make a difference. I also tried setting a script to run at logout in lightdm, but that didn't seem to work either: it did kill the original systemd process tree running gvfs, but then it looks like another one gets spun up to replace it, and I wind up with the same issue. Anyone have any suggestions how to work around this? Thanks, DR
On Fri, 24 Jan 2020 at 20:50, David Rosenstrauch <darose@darose.net> wrote:
I've noticed recently that even after I log out of my desktop env (XFCE) there is a process tree left hanging around running "systemd --user" under my user ID (with a bunch of gvfs child processes running under it).
https://github.com/systemd/systemd/blob/v240/NEWS#L299 -- damjan
On 2020-01-25 11:28 am, Damjan Georgievski via arch-general wrote:
On Fri, 24 Jan 2020 at 20:50, David Rosenstrauch <darose@darose.net> wrote:
I've noticed recently that even after I log out of my desktop env (XFCE) there is a process tree left hanging around running "systemd --user" under my user ID (with a bunch of gvfs child processes running under it).
Thanks much for responding. Turned out that the systemd issue was actually a bit of a red herring, and the real problem was with syslog-ng: https://bugs.archlinux.org/task/65206 DR
Hi DR,
I've noticed recently that even after I log out of my desktop env (XFCE) there is a process tree left hanging around running "systemd --user" under my user ID (with a bunch of gvfs child processes running under it).
Me too. It's been like that for a long time. If you do ‘loginctl user-status $user’ for that user, does it show a process under the session-*.scope? I have /usr/lib/geoclue-2.0/demos/agent here. If so, it's that process that's keeping the session open and thus gvfs lives on because it's ‘required’. Killing just geoclue's PID makes the session disappear after a few seconds as the session doesn't get reused. -- Cheers, Ralph.
participants (3)
-
Damjan Georgievski
-
David Rosenstrauch
-
Ralph Corderoy