From ddcb33bdc06f940de9ae93786e07b6bd62432f66 Mon Sep 17 00:00:00 2001
From: =?utf8?q?Miguel=20=C3=81ngel=20Arruga=20Vivas?=
 <rosen644835@gmail.com>
Date: Mon, 4 Nov 2019 15:55:22 +0100
Subject: [PATCH] doc: cgroups: Remove unwanted references to systemd
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

The non-systemd configurations do not create system neither user
control groups.  The title of the diagram referenced systemd too.

Signed-off-by: Miguel Ángel Arruga Vivas <rosen644835@gmail.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
---
 docs/cgroups.html.in | 13 +++----------
 1 file changed, 3 insertions(+), 10 deletions(-)

diff --git a/docs/cgroups.html.in b/docs/cgroups.html.in
index 081ba2eae1..78dede1bba 100644
--- a/docs/cgroups.html.in
+++ b/docs/cgroups.html.in
@@ -155,24 +155,17 @@ $ROOT
       named <code>$VMNAME.libvirt-{qemu,lxc}</code>. Each consumer is associated
       with exactly one partition, which also have a corresponding cgroup usually
       named <code>$PARTNAME.partition</code>. The exceptions to this naming rule
-      are the three top level default partitions, named <code>/system</code> (for
-      system services), <code>/user</code> (for user login sessions) and
-      <code>/machine</code> (for virtual machines and containers). By default
-      every consumer will of course be associated with the <code>/machine</code>
-      partition.
+      is the top level default partition for virtual machines and containers
+      <code>/machine</code>.
     </p>
 
     <p>
-      Given this, a possible systemd cgroups layout involving 3 qemu guests,
+      Given this, a possible non-systemd cgroups layout involving 3 qemu guests,
       3 lxc containers and 2 custom child slices, would be:
     </p>
 
     <pre>
 $ROOT
-  |
-  +- system
-  |   |
-  |   +- libvirtd.service
   |
   +- machine
       |
-- 
2.47.2