From: Mike Yuan Date: Tue, 10 Oct 2023 10:08:08 +0000 (+0800) Subject: man/systemd.exec: document behavior of SetLoginEnvironment= when unset X-Git-Tag: v255-rc1~286 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=3759a174188503178005f7f44b16d19f12ed0b35;p=thirdparty%2Fsystemd.git man/systemd.exec: document behavior of SetLoginEnvironment= when unset Follow-up for 854eca4a95993bb1bd77a18de39efe1ed1a44bbd Addresses https://github.com/systemd/systemd/pull/29493#discussion_r1351980046 --- diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index e648aeedaa0..52cce9bc308 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -699,12 +699,12 @@ SetLoginEnvironment= - Takes a boolean parameter. If true, $HOME, $LOGNAME, - and $SHELL environment variables will be set for system services even if - User= is not set, i.e. when the default user root is used. - If false, the mentioned variables are not set by systemd, no matter whether User= - is set or not. This option normally has no effect on user services, since these variables are typically - inherited from user manager's own environment anyway. + Takes a boolean parameter that controls whether to set $HOME, + $LOGNAME, and $SHELL environment variables. If unset, this is + controlled by whether User= is set. If true, they will always be set for system services, + i.e. even when the default user root is used. If false, the mentioned variables are not set + by systemd, no matter whether User= is used or not. This option normally has no effect + on user services, since these variables are typically inherited from user manager's own environment anyway.