diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-04-09 20:40:45 -0400 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-04-21 00:21:32 -0400 |
| commit | 97e5530cf2076a2b4fc55755917262607aaa6338 (patch) | |
| tree | d5e81a1e8d0a3ad8780ca818cbb9c08bfcd9255e /man/logind.conf.xml | |
| parent | 65eb37f8fcf0c82db0d9b600bb804adf7ead0327 (diff) | |
| download | systemd-97e5530cf2076a2b4fc55755917262607aaa6338.tar.gz | |
logind: flip KillUserProcesses to on by default
This ensures that users sessions are properly cleaned up after.
The admin can still enable or disable linger for specific users to allow
them to run processes after they log out. Doing that through the user
session is much cleaner and provides better control.
dbus daemon can now be run in the user session (with --enable-user-session,
added in 1.10.2), and most distributions opted to pick this configuration.
In the normal case it makes a lot of sense to kill remaining processes.
The exception is stuff like screen and tmux. But it's easy enough to
work around, a simple example was added to the man page in previous
commit. In the long run those services should integrate with the systemd
users session on their own.
https://bugs.freedesktop.org/show_bug.cgi?id=94508
https://github.com/systemd/systemd/issues/2900
Diffstat (limited to 'man/logind.conf.xml')
| -rw-r--r-- | man/logind.conf.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/man/logind.conf.xml b/man/logind.conf.xml index 10a23955a4..6e587c3561 100644 --- a/man/logind.conf.xml +++ b/man/logind.conf.xml @@ -124,7 +124,7 @@ corresponding to the session and all processes inside that scope will be terminated. If false, the scope is "abandonded", see <citerefentry><refentrytitle>systemd.scope</refentrytitle><manvolnum>5</manvolnum></citerefentry>, - and processes are not killed. Defaults to <literal>no</literal>.</para> + and processes are not killed. Defaults to <literal>yes</literal>.</para> <para>In addition to session processes, user process may run under the user manager unit <filename>user@.service</filename>. Depending on the linger |