From 706a3df4beba0fb14c4b0e6cb8920721c850ac99 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= <zbyszek@in.waw.pl>
Date: Tue, 22 May 2018 12:19:27 +0200
Subject: [PATCH] man: recommend After= with Requisite=

Fixes #8309.
---
 man/systemd.unit.xml | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index b6f4728b00..14dd4b0694 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -590,10 +590,12 @@
       <varlistentry>
         <term><varname>Requisite=</varname></term>
 
-        <listitem><para>Similar to <varname>Requires=</varname>.
-        However, if the units listed here are not started already,
-        they will not be started and the transaction will fail
-        immediately.</para>
+        <listitem><para>Similar to <varname>Requires=</varname>. However, if the units listed here
+        are not started already, they will not be started and the starting of this unit will fail
+        immediately. <varname>Requisite=</varname> does not imply an ordering dependency, even if
+        both units are started in the same transaction. Hence this setting should usually be
+        combined with <varname>After=</varname>, to ensure this unit is not started before the other
+        unit.</para>
 
         <para>When <varname>Requisite=b.service</varname> is used on
         <filename>a.service</filename>, this dependency will show as