On Tue, Aug 02, 2022 at 08:30:48AM +0200, Michael Biebl wrote: > We only document KillUserProcesses=yes in README.Debian as we deviate from > the upstream defaults here.
The text does both: It documents the deviation and warns users of
possibly unexpected behavior.
>
> > > 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.
Wording should be improved then; I didn't manage to find out where these
things are actually stored -- but let's look at whether a change is
indicated first:
> 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"?
It appears it does need to be enabled. At least that was the
recommendation in [1016475]. The original [946645], while confirming
that this happens, did not manage to find where precisely it is coming
from, but enabling lingering was a working fix.
I lack the big picture of all the interworking components around logind,
but the observation confirmed both in these issues and also outside of
Debian[1] ("To fix, do *all* of the following steps") is that at least
in some circumstances (such as when following the steps outlined in the
two referenced issues), just having KillUserProcesses=no is
insufficient.
BR
c
[1]:
https://superuser.com/questions/1372963/how-do-i-keep-systemd-from-killing-my-tmux-sessions
[946645]: https://bugs.debian.org/946645
[1016475]://bugs.debian.org/1016475
--
To use raw power is to make yourself infinitely vulnerable to greater powers.
-- Bene Gesserit axiom
signature.asc
Description: PGP signature
