Systemd 230 Is Upsetting Some Over Its KillUserProcess Setting
Written by Michael Larabel in systemd on 28 May 2016 at 12:29 PM EDT. 50 Comments
SYSTEMD --
Systemd 230 was released just last week and it has taken heat not only for opening up FBDEV to potential security issues, which already reverted, but also for changing the default behavior of user processes.

Systemd 230 made a change where KillUserProcess defaults to yes. This terminates user processes that are part of the user session scope when the user logs out. This is causing problems for ssh-agent, screen, and other common Linux processes.

If you would like some weekend reading, there's a lengthy Fedora devel thread about this issue. Additionally, there's a Debian bug report about the problem of systemd now killing background processes after a user logs out.

This new functionality can be disabled by editing your systemd configuration and disabling KillUserProcess.
About The Author
Author picture

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter or contacted via MichaelLarabel.com.

Related systemd News
Popular News This Week