From afbc75e686dfe108db5fda1a10e0e5670d672db5 Mon Sep 17 00:00:00 2001 From: Daniel Black Date: Thu, 14 Dec 2017 15:51:23 +1100 Subject: [PATCH] man: systemd.unit: move note about clearing lists (#7621) This is mainly for drop-in files. --- man/systemd.unit.xml | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 49f82c1..5cd8be3 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -1603,13 +1603,6 @@ ExecStart=/usr/sbin/foo-daemon disadvantage that some future updates by the vendor might be incompatible with the local changes. - Note that for drop-in files, if one wants to remove - entries from a setting that is parsed as a list (and is not a - dependency), such as ConditionPathExists= (or - e.g. ExecStart= in service units), one needs - to first clear the list before re-adding all entries except the - one that is to be removed. See below for an example. - This also applies for user instances of systemd, but with different locations for the unit files. See the section on unit load paths for further details. @@ -1681,7 +1674,12 @@ AssertPathExists=/srv/www Nice=0 PrivateTmp=yes - Note that dependencies (After=, etc.) + Note that for drop-in files, if one wants to remove + entries from a setting that is parsed as a list (and is not a + dependency), such as AssertPathExists= (or + e.g. ExecStart= in service units), one needs + to first clear the list before re-adding all entries except the + one that is to be removed. Dependencies (After=, etc.) cannot be reset to an empty list, so dependencies can only be added in drop-ins. If you want to remove dependencies, you have to override the entire unit. -- 2.7.4