From: Lennart Poettering <lennart@poettering.net>
Date: Tue, 5 Nov 2024 12:15:36 +0000 (+0100)
Subject: man: don't claim SELinuxContext= only worked in the system service manager
X-Git-Tag: v256.8~35
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=5a2ffc543b20fdae10c41a3df838b3ea9bae3399;p=thirdparty%2Fsystemd.git

man: don't claim SELinuxContext= only worked in the system service manager

Fixes: #34840
(cherry picked from commit ecbe9ae5a0952d968c57e59dda4a42b72e5b5e6d)
---

diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index 21527f756d6..8e72e9c0609 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -875,8 +875,6 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
   <refsect1>
     <title>Mandatory Access Control</title>
 
-    <xi:include href="system-only.xml" xpointer="plural"/>
-
     <variablelist class='unit-directives'>
 
       <varlistentry>
@@ -903,6 +901,8 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
         prefixed by <literal>-</literal>, all errors will be ignored. This setting has no effect if AppArmor
         is not enabled. This setting does not affect commands prefixed with <literal>+</literal>.</para>
 
+        <xi:include href="system-only.xml" xpointer="singular"/>
+
         <xi:include href="version-info.xml" xpointer="v210"/>
         </listitem>
       </varlistentry>
@@ -921,6 +921,8 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
         value may be specified to unset previous assignments. This does not affect commands prefixed with
         <literal>+</literal>.</para>
 
+        <xi:include href="system-only.xml" xpointer="singular"/>
+
         <xi:include href="version-info.xml" xpointer="v218"/></listitem>
       </varlistentry>