From 22a705631d575388116c913c57303e572e4c1d67 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Sat, 20 Jan 2018 10:45:02 +1100 Subject: [PATCH] man: clarify that Requires stop propagation only applies to explit requests Follow-up for e79eabdb1becc93cf4afc909aa18dc40c931eab5. There was an apparent contradiction: man/systemd.unit says for Requires=: Besides, with or without specifying After=, this unit will be deactivated if one of the other units get deactivated. Also, some unit types may deactivate on their own (for example, a service process may decide to exit cleanly, or a device may be unplugged by the user), which is not propagated to units having a Requires= dependency. Fixes #7870. --- man/systemd.unit.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 19a6db7f65b..90ca378e847 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -505,8 +505,8 @@ Configures requirement dependencies on other units. If this unit gets activated, the units listed here will be activated as well. If one of the other units fails to activate, and an ordering dependency After= on the failing unit is set, this unit will not be started. Besides, with or without - specifying After=, this unit will be deactivated if one of the other units get deactivated. - This option may be specified more than once or multiple space-separated units may be + specifying After=, this unit will be stopped if one of the other units is explicitly + stopped. This option may be specified more than once or multiple space-separated units may be specified in one option in which case requirement dependencies for all listed names will be created. Note that requirement dependencies do not influence the order in which services are started or stopped. This has to be configured independently with the After= or Before= options. If a unit -- 2.47.3