From e8f4bf33d8a6123ad8ae3955c989e36972f4884d Mon Sep 17 00:00:00 2001
From: dgcampea <dgcampea@outlook.com>
Date: Sat, 26 Jun 2021 13:23:20 +0100
Subject: [PATCH] man: fix incorrect description regarding DynamicUser= and
 StateDirectory=

---
 man/systemd.exec.xml | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index b17635c5d24..1789d97ce3f 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -1290,16 +1290,15 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
         <varname>RootDirectory=</varname> or <varname>RootImage=</varname> these paths always reside on the host and
         are mounted from there into the unit's file system namespace.</para>
 
-        <para>If <varname>DynamicUser=</varname> is used in conjunction with
-        <varname>StateDirectory=</varname>, the logic for <varname>CacheDirectory=</varname> and
-        <varname>LogsDirectory=</varname> is slightly altered: the directories are created below
-        <filename>/var/lib/private</filename>, <filename>/var/cache/private</filename> and
-        <filename>/var/log/private</filename>, respectively, which are host directories made inaccessible to
+        <para>If <varname>DynamicUser=</varname> is used, the logic for <varname>CacheDirectory=</varname>,
+        <varname>LogsDirectory=</varname> and <varname>StateDirectory=</varname> is slightly altered: the directories are created below
+        <filename>/var/cache/private</filename>, <filename>/var/log/private</filename> and <filename>/var/lib/private</filename>,
+        respectively, which are host directories made inaccessible to
         unprivileged users, which ensures that access to these directories cannot be gained through dynamic
         user ID recycling. Symbolic links are created to hide this difference in behaviour. Both from
         perspective of the host and from inside the unit, the relevant directories hence always appear
-        directly below <filename>/var/lib</filename>, <filename>/var/cache</filename> and
-        <filename>/var/log</filename>.</para>
+        directly below <filename>/var/cache</filename>, <filename>/var/log</filename> and
+        <filename>/var/lib</filename>.</para>
 
         <para>Use <varname>RuntimeDirectory=</varname> to manage one or more runtime directories for the unit and bind
         their lifetime to the daemon runtime. This is particularly useful for unprivileged daemons that cannot create
-- 
2.47.3