From b292066890ae92c8d6d8d04c9261970e79a8a8be Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Thu, 7 Dec 2017 09:14:19 +0100 Subject: [PATCH] man: mention BoundsBy=, ConsistsOf=, RequisiteOf= Fixes #7043. --- man/systemd.unit.xml | 27 ++++++++++++++++++++++++--- 1 file changed, 24 insertions(+), 3 deletions(-) diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 159f629498..a4de424835 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -537,7 +537,14 @@ Similar to Requires=. However, if the units listed here are not started already, they will not be started and the transaction will fail - immediately. + immediately. + + When Requisite=b.service is used on + a.service, this dependency will show as + RequisiteOf=a.service in property listing of + b.service. RequisiteOf= + dependency cannot be specified directly. + @@ -575,7 +582,14 @@ enters inactive state, but also one that is bound to another unit that gets skipped due to a failed condition check (such as ConditionPathExists=, ConditionPathIsSymbolicLink=, … — see below) will be stopped, should it be running. Hence, in many cases it is best to combine - BindsTo= with After=. + BindsTo= with After=. + + When BindsTo=b.service is used on + a.service, this dependency will show as + BoundBy=a.service in property listing of + b.service. BoundBy= + dependency cannot be specified directly. + @@ -586,7 +600,14 @@ restarting of units. When systemd stops or restarts the units listed here, the action is propagated to this unit. Note that this is a one-way dependency — changes to this unit do not - affect the listed units. + affect the listed units. + + When PartOf=b.service is used on + a.service, this dependency will show as + ConsistsOf=a.service in property listing of + b.service. ConsistsOf= + dependency cannot be specified directly. +