From: Shihao Ren Date: Tue, 30 Jun 2026 06:18:14 +0000 (+0800) Subject: man: fix wrong KillUserProcesses= default in systemd-run(1) X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=bbb863a008ec29ffd7da0fab518f841f20664fd7;p=thirdparty%2Fsystemd.git man: fix wrong KillUserProcesses= default in systemd-run(1) systemd-run(1) hard-coded "the default" wording for KillUserProcesses=, but the actual compile-time default is determined by the -Ddefault-kill-user-processes= meson build option, which distributions set differently at packaging time. Consistent with logind.conf(5). Fixes: #42805 Signed-off-by: Shihao Ren --- diff --git a/man/systemd-run.xml b/man/systemd-run.xml index bb90f352657..e66672f7168 100644 --- a/man/systemd-run.xml +++ b/man/systemd-run.xml @@ -1,6 +1,9 @@ + "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ + +%entities; +]> screen as a user unit has the advantage that it is not part of the session scope. If KillUserProcesses=yes is configured in - logind.conf5, - the default, the session scope will be terminated when the user logs - out of that session. + logind.conf5 + (defaults to &KILL_USER_PROCESSES;), the session scope will be terminated when + the user logs out of that session. The user@.service is started automatically when the user first logs in, and stays around as long as at least one