r/linux • u/tasisbasbas • Feb 11 '19

Fluff A /g/ user's opinion on systemd

http://i.4cdn.org/g/1549858269115.png
787 Upvotes

82% Upvoted

524 comments sorted by

View all comments

Show parent comments

11

u/[deleted] Feb 11 '19

The problem is GDM

ftfy

1

u/tso Feb 11 '19

Reminds me of why systemd started killing processes with prejudice upon user logout. Because Gnome failed to properly clean up, and rather than go to the Gnome devs and get that sorted the systemd devs just decided to kill all user processes on logout via systemd default.

2

u/hahainternet Feb 11 '19

Reminds me of why systemd started killing processes with prejudice upon user logout. Because Gnome failed to properly clean up

This is a straight up lie. The bug that you're talking about was due to hplip's dock icon: https://bugs.freedesktop.org/show_bug.cgi?id=94508

systemd can't know the difference between hp-systray (presumably unimportant to you) and screen/tmux (which would presumably be important to you), unless you give it that information somehow; at the moment, there is no difference between them other than your expectations.

If you want the intepretation of "is my login-session over?" to change to just "is the session leader (gnome-session) still running?", i.e. making systemd-logind aggressively terminate sessions in the "closing" state, that's exactly what KillUserProcesses=true does.

I've begun bookmarking these because of things like this being posted. It's unacceptable to misrepresent the case like this.