Control: severity -1 wishlist Control: tags -1 + moreinfo
Am 01.08.22 um 23:23 schrieb chrysn:
Package: systemd Version: 251.3-1 Severity: normal File: /usr/share/doc/systemd/README.Debian.gz The README.Debian file duefully documents the surprising[1] effects that happen when using tmux or similar under in a logind session. However, it only covers the KillUserProcesses part of things (a mechanism that Debian thankfully disables by default), and not the linger part, which has a similar (if not the same) effect and is set to kill by default. Suggested new text, based on the current one:KillUserProcesses and linger behavior in Debian =============================================== If KillUserProcesses=yes is configured in logind.conf(5), the session scope will be terminated when the user logs out of that session. Likewise, processes launched by users configured as Linger=no (see loginctl(1)) are terminated. See logind.conf(5): | Note that setting KillUserProcesses=yes will break tools like screen(1) and | tmux(1), unless they are moved out of the session scope. The default for KillUserProcesses in /etc/systemd/logind.conf is set to "yes" in upstream systemd, though Debian defaults to "no" (see #825394).
We only document KillUserProcesses=yes in README.Debian as we deviate from the upstream defaults here.
The default Linger value for users is set to "no", and may need to be altered with `loginctl enable-linger ${USER}` to keep screen and tmux useful.
This reads like there would be a "Linger=yes/no" value in logind.conf, which is misleading. It is also incorrect, as you don't need to enable lingering if you want tmux to survive a log out (which was the reason for setting KillUserProcesses=no in Debian). Then again, I don't understand what you mean by "keep useful"?
That said, since we don't deviate from the upstream defaults here, I don't like adding this information to README.Debian.
OpenPGP_signature
Description: OpenPGP digital signature
