man: only the system manager does not pass vars in ManagerEnvironment=

User managers always pass their environment on to their children.
Make that clear in the description of ManagerEnvironment= which
states that none of those args will get passed to child processes of
service managers.

diff --git a/man/systemd-system.conf.xml b/man/systemd-system.conf.xml
index d39928ec239b23115c2f279ece2c087a67fe589d..1ac0077d86853fce216bcd0706eef7e9f0e4d167 100644 (file)
--- a/man/systemd-system.conf.xml
+++ b/man/systemd-system.conf.xml
@@ -342,10 +342,10 @@
         <term><varname>ManagerEnvironment=</varname></term>
 
         <listitem><para>Takes the same arguments as <varname>DefaultEnvironment=</varname>, see above. Sets
-        environment variables just for the manager process itself. These variables are not inherited by
-        processes spawned by the service manager, use <varname>DefaultEnvironment=</varname> 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.</para>
+        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 <varname>DefaultEnvironment=</varname>
+        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.</para>
 
         <para>Setting environment variables for the manager process may be useful to modify its behaviour.
         See <ulink url="https://systemd.io/ENVIRONMENT">ENVIRONMENT</ulink> for a descriptions of some