From bb28a6c0b68a4a9dc2aa33972b3419680d333c05 Mon Sep 17 00:00:00 2001 From: Vladimir Panteleev Date: Sat, 27 Jul 2024 11:43:47 +0000 Subject: [PATCH] man: improve ManagerEnvironment documentation - Improve wording for explanation when these variables are inherited - Clarify that these variables are not placed in the process environment block, so /proc/PID/environ cannot be used as a debugging tool (cherry picked from commit 6c1e0823b04525716d9ee0031a2b6735d3f7dfa4) (cherry picked from commit 5cf0c45f64079430b0b7c12ad323f238386260b0) (cherry picked from commit 79f335d0ef2d3c35fdf4c19988c711a3abd31ee0) --- man/systemd-system.conf.xml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/man/systemd-system.conf.xml b/man/systemd-system.conf.xml index e106dabaf4a..c1c4eacef37 100644 --- a/man/systemd-system.conf.xml +++ b/man/systemd-system.conf.xml @@ -417,10 +417,12 @@ ManagerEnvironment= Takes the same arguments as DefaultEnvironment=, see above. Sets - environment variables just for the manager process itself. In contrast to user managers, these variables - are not inherited by processes spawned by the system manager, use DefaultEnvironment= + environment variables for the manager process itself. These variables are inherited by processes + spawned by user managers, but not the system manager - use DefaultEnvironment= for that. Note that these variables are merged into the existing environment block. In particular, in - case of the system manager, this includes variables set by the kernel based on the kernel command line. + case of the system manager, this includes variables set by the kernel based on the kernel command line. + As with DefaultEnvironment=, this environment block is internal, and changes are not + reflected in the manager's /proc/PID/environ. Setting environment variables for the manager process may be useful to modify its behaviour. See ENVIRONMENT for a descriptions of some