2 ms·
The response to the bug report: Hello, You should quote the full changelog and not just the part that is 'bad' in your mind. >systemd-logind will now by defau
by mcguire 10y ago
The response to the bug report:
Hello,
You should quote the full changelog and not just
the part that is 'bad' in your mind.
>systemd-logind will now by default terminate user processes that are part of
>the user session scope unit (session-XX.scope) when the user logs out. This
>behavior is controlled by the KillUserProcesses= setting in logind.conf, and
>the previous default of "no" is now changed to "yes".
For debian it would be enough to set this to "no" again with
--without-kill-user-processes option to "configure"
>This means that user sessions will be properly cleaned up after, but
>additional steps are necessary to allow intentionally long-running processes
>to survive logout.
Here comes the important part. Seems like the systemd-devs are working on a
way to allow intentionally long-running processes in a specific user scope.
And here is another way for allowing these long-running processes:
>While the user is logged in at least once, user@.service is running, and any
>service that should survive the end of any individual login session can be
>started at a user service or scope using systemd-run. systemd-run(1) man
>page has been extended with an example which shows how to run screen in a
>scope unit underneath user@.service. The same command works for tmux.
And another way for allowing long-running processes.
>After the user logs out of all sessions, user@.service will be terminated
>too, by default, unless the user has "lingering" enabled. To effectively
>allow users to run long-term tasks even if they are logged out, lingering
>must be enabled for them. See loginctl(1) for details. The default polkit
>policy was modified to allow users to set lingering for themselves without
>authentication.
>
>Previous defaults can be restored at compile time by the
>--without-kill-user-processes option to "configure"
You see? No reason to complain about.
Best regards
Christian Rebischke.
tl;dr: You can configure it not to, or you can accept that Linux is about as much a "Unix" as AIX, Irix, or HP-UX and join them in the wonderful land of the future, which suspiciously resembles the time before all the non-standard vendors died.
I'll stop now, before I make Linus on a backwards compatibility rant look like a choir boy in church.
- TwoNineFive 10y agoWow. Christian Rebischke's response to this reasonable, mild-mannered, bug report, is unbelievably hostile. Now he's out on Twitter describing the bug as a "hate-report". With any hope, a future employer will find this, put it in front of him, and ask if that's the kind of behavior that should be expected of him. Before turning him around and out the door.