From 4aabca00581f262fc0c5a1a31ab3978e68cb0ddf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Fri, 14 Sep 2018 16:39:47 +0200 Subject: [PATCH] man: remove recommendation to pull in slices from slices.target That recommendation is likely to cause more trouble and for pretty much all end-user units is not useful. Let's recommend relying on the implicit dependency instead. Fixes #10015. --- man/systemd.special.xml | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/man/systemd.special.xml b/man/systemd.special.xml index 38006c6abd..0d25e40d03 100644 --- a/man/systemd.special.xml +++ b/man/systemd.special.xml @@ -596,14 +596,18 @@ A special target unit that sets up all slice units (see systemd.slice5 - for details) that shall be active after boot. By default the generic - system.slice slice unit, as well as the root slice unit - -.slice, is pulled in and ordered before this unit (see + for details) that shall always be active after boot. By default the generic + system.slice slice unit as well as the root slice unit + -.slice are pulled in and ordered before this unit (see below). - It's a good idea to add WantedBy=slices.target lines to the - [Install] section of all slices units that may be installed - dynamically. + Adding slice units to slices.target is generally not + necessary. Instead, when some unit that uses Slice= is started, the + specified slice will be started automatically. Adding + WantedBy=slices.target lines to the [Install] + section should only be done for units that need to be always active. In that case care + needs to be taken to avoid creating a loop through the automatic dependencies on + "parent" slices.