Your message dated Thu, 24 Aug 2023 12:16:24 +0200
with message-id <af25bb6f-4d04-4ca5-bd93-c653c7609...@debian.org>
and subject line Re: Bug#1016500: README.Debian documents KillUserProcesses but
not Linger
has caused the Debian Bug report #1016500,
regarding README.Debian documents KillUserProcesses but not Linger
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1016500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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).
>
> 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.
[1]: https://bugs.debian.org/1016475
-- Package-specific info:
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.123
ii libacl1 2.3.1-1
ii libaudit1 1:3.0.7-1+b1
ii libblkid1 2.38-6
ii libc6 2.33-8
ii libcap2 1:2.44-1
ii libcryptsetup12 2:2.5.0-1
ii libfdisk1 2.38-6
ii libgcrypt20 1.10.1-2
ii libkmod2 30+20220630-3
ii liblz4-1 1.9.3-2
ii liblzma5 5.2.5-2.1
ii libmount1 2.38-6
ii libseccomp2 2.5.4-1+b1
ii libselinux1 3.4-1+b1
ii libssl3 3.0.5-1
ii libsystemd-shared 251.3-1
ii libsystemd0 251.3-1
ii libzstd1 1.5.2+dfsg-1
ii mount 2.38-6
Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.14.0-2
ii ntpsec [time-daemon] 1.2.1+dfsg1-7+b1
Versions of packages systemd suggests:
ii libfido2-1 1.11.0-1+b1
ii libtss2-esys-3.0.2-0 3.2.0-1+b1
ii libtss2-mu0 3.2.0-1+b1
ii libtss2-rc0 3.2.0-1+b1
ii policykit-1 0.105-33
pn systemd-boot <none>
ii systemd-container 251.3-1
pn systemd-homed <none>
pn systemd-userdbd <none>
Versions of packages systemd is related to:
ii dbus-user-session 1.14.0-2
pn dracut <none>
ii initramfs-tools 0.142
pn libnss-systemd <none>
ii libpam-systemd 251.3-1
ii udev 251.3-1
-- no debconf information
--
To use raw power is to make yourself infinitely vulnerable to greater powers.
-- Bene Gesserit axiom
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Tue, 2 Aug 2022 08:30:48 +0200 Michael Biebl <bi...@debian.org> wrote:
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.
Given this reasoning, I'm closing this bug report as wontfix.
We do have extensive man pages going in detail about user sessions and
lingering and I don't think we need to duplicate this in README.Debian.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
