Re:Systemd, ten years later: a historical and technical retr...
by tyingq on Sunday May 03, 2020 @11:12PM
(#23064191)
It is the default.
This behavior is controlled by the KillUserProcesses= setting in logind.conf, and the previous default of "no" is now changed to "yes".
https://github.com/systemd/systemd/blob/2d4f8cf467b6825c9127...
Re:Systemd, ten years later: a historical and technical retr...
by frio on Sunday May 03, 2020 @11:27PM
(#23064268)
This is one of those fun situations where everyone's right.
The upstream default has changed, but CentOS still uses the old default.
Re:Systemd, ten years later: a historical and technical retr...
by m45t3r on Monday May 04, 2020 @12:27AM
(#23064549)
Almost every distro I know turns this option off by default, including Arch, NixOS and Debian (the last one I am not sure).
Re:Systemd, ten years later: a historical and technical retr...
by fsh on Monday May 04, 2020 @03:18AM
(#23065368)
It defaults to "no" on Debian 10. Maybe Fedora changed the default?
Re:Systemd, ten years later: a historical and technical retr...
by Conan_Kudo on Monday May 04, 2020 @04:04AM
(#23065579)
Fedora does not have this feature on: https://src.fedoraproject.org/rpms/systemd/blob/265d91aff516...
Re:Systemd, ten years later: a historical and technical retr...
by dTal on Monday May 04, 2020 @07:44AM
(#23066823)
That's most interesting, given that both systemd and Fedora are Red Hat products. If there's one distro that would use the systemd defaults, I would expect it to be Fedora. Who exactly are these defaults for, then?
Re:Systemd, ten years later: a historical and technical retr...
by Conan_Kudo on Monday May 04, 2020 @02:21PM
(#23071450)
I've mainly seen it switched on for appliances and things that don't really have a legacy of this behavior.
It's not switched on in RHEL or Fedora. It's likely to never be so.
Re:Systemd, ten years later: a historical and technical retr...
by ttctciyf on Sunday May 03, 2020 @10:43PM
(#23064049)
Switching to CentOS in order to use screen is not an appealing option, and the config appears not to work on my current distro (that might be my poor testing, but it's certainly not the default anyhow.)
I understand Slackware still lacks systemd, so maybe that's a better choice for me :)
I just tried it on a fully up-to-date CentOS 8 box (which uses systemd), and it worked perfectly fine: after logging back in through ssh, `screen -r` restored the screen session as expected.
From what I have read, that screen session would only be killed if I had set KillUserProcesses=yes on /etc/systemd/logind.conf, which is not the default.