Hi Guus, Am 26.05.2016 um 18:16 schrieb Guus Sliepen: >> systemd-logind will now by default terminate user processes that are >> part of the user session scope unit (session-XX.scope) when the user >> logs out. > > It is now indeed the case that any background processes that were still > running are killed automatically when the user logs out of a session, > whether it was a desktop session, a VT session, or when you SSHed into a > machine. > > Now you can no longer expect a long running background processes to > continue after logging out.
Unless you use systemd-run/linger, then you can still expect those background processes to continue to run. But I guess this wasn't your point. I believe this breaks the expecations of > many users. For example, you can no longer start a screen or tmux > session, log out, and expect to come back to it. For this reason, I > think it is a bad decision on the part of the systemd maintainers to > enable this feature by default, and it should rather be disabled by > default in Debian, either by compiling systemd with > --without-kill-user-processes or by setting KillUserProcesses=no in > /etc/systemd/logind.conf. The new requirement of having to enable lingering and starting tmux/screen/nohup/ via systemd-run can certainly be considered a nuisance and something our users are not necessarily aware of. I share that concern. So a NEWS.Debian entry would be the least we should do. And maybe documenting it in the release notes. That all said, we'll discuss that within the team. I couldn't get hold of Martin on irc, so this might take a couple of days (I won't be around much over the weekend). I personally need to do some more research first, e.g. how that affects systemd/dbus user sessions. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature