summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMaxime de Roucy <maxime.deroucy@gmail.com>2016-07-31 14:43:23 +0200
committerMaxime de Roucy <maxime.deroucy@gmail.com>2016-07-31 15:00:59 +0200
commitc23b2c70bf65d3fdf869c60eee4072b1d4e5905b (patch)
tree4a47caf98d3e4a54f2befdb65db46098d9fdda94
parent65c1cdb282d33f72d2c247dfe13dd7c8baa8f302 (diff)
documentation: cgroup-v1 and systemd user instance
Explain in the systemd.resource-control man that systemd user instance can't use resource control on cgroup-v1.
-rw-r--r--man/systemd.resource-control.xml7
1 files changed, 7 insertions, 0 deletions
diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml
index 76f3370b53..cb8c896e5c 100644
--- a/man/systemd.resource-control.xml
+++ b/man/systemd.resource-control.xml
@@ -127,6 +127,13 @@
settings of a unit for a given resource type are for the other hierarchy type, the settings are translated and
applied. If there are any valid settings for the hierarchy in use, all translations are disabled for the resource
type. Mixing the two types of settings on a unit can lead to confusing results.</para>
+
+ <para>Legacy control group hierarchy (see <ulink
+ url="https://www.kernel.org/doc/Documentation/cgroup-v1/cgroups.txt">cgroups.txt</ulink>), also called cgroup-v1,
+ doesn't allow safe delegation of controllers to unprivileged processes. If the system use legacy control group
+ hierarchy, resource control is disabled for systemd user instance, see
+ <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
+ </para>
</refsect1>
<refsect1>