On Mon, May 30, 2016 at 10:22:13AM +0000, Ian Young wrote:
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. I believe this breaks the expectations of many users.
Yes, it breaks the well established practice that the controlling terminal sends all its child processes a HUP signal on logout, and that the default signal handler will kill such processes, and if the process wants to remain running it therefore establishes a signal handler to properly receive and handle the HUP signal so that it is not terminated. If processes are not being terminated on logout when they should be, then it is the non-terminating processes fault as the process has taken action to set up a non-default signal hangler to receive the HUP signal to achieve this effect. It is most certainly not the responsibility of systemd to kill processes on logout! With these critical and non-sensical changes to system behaviour that is well without the established remit of the init process the systemd developers are fast losing what little respect I might have had for them. Cheers Michael.