3 ms·
> Still, seems like this should be done at the distro package level. This can be done at the distro package level. Packagers would edit /etc/systemd/logind.con
by justabystander 10y ago
> Still, seems like this should be done at the distro package level.
This can be done at the distro package level. Packagers would edit /etc/systemd/logind.conf and set KillUserProcesses=no to disable it. It's a single line change if people don't like the new default. The behavior itself (killing user processes when the session ends) is quite sensible, and should have been the default over a decade ago, but people got used to terrible defaults and are now complaining.
This is handled at the packager/admin level, but they merged a patch two days ago (https://github.com/systemd/systemd/pull/3373 https://github.com/systemd/systemd/pull/3373) to fix the policy to let users manage it themselves with loginctl enable-linger. I think it missed the v230 merge window, but could easily be backported individually or at the distro level until the next release.
So, not only can the behavioral decision be managed entirely at the distro level, that decision can be punted down to the individual user if they don't want to explicitly mark the processes they want to continue running.
- icebraining 10y agoWhat I'm saying is that this exception should be added to tmux at the distro package level, they shouldn't push to have it included upstream. In any case, wasn't killing user processes already the norm except for the ones which called daemon() or equivalent? And won't the new system kill user processes except for the ones who call StartTransientUnit? I'm having some trouble understanding the improvement, except for the short-term gain until the broken processes start calling the new API.