3 ms·
It is the default. This behavior is controlled by the KillUserProcesses= setting in logind.conf, and the previous default of "no" is now ch
by tyingq 7y ago
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/2d4f8cf467b6825c91276808250823a29ab461fe/NEWS#L4356 https://github.com/systemd/systemd/blob/2d4f8cf467b6825c9127...
- frio 7y agoThis is one of those fun situations where everyone's right. The upstream default has changed, but CentOS still uses the old default.
- m45t3r 7y agoAlmost every distro I know turns this option off by default, including Arch, NixOS and Debian (the last one I am not sure).
- fsh 7y agoIt defaults to "no" on Debian 10. Maybe Fedora changed the default?
- Conan_Kudo 7y agoFedora does not have this feature on: https://src.fedoraproject.org/rpms/systemd/blob/265d91aff516c0e0a13da9ed7613cd0cbfba9e9c/f/systemd.spec#_369 https://src.fedoraproject.org/rpms/systemd/blob/265d91aff516...
- dTal 7y agoThat'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?
- Conan_Kudo 7y agoI'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.