man: recommend After= with Requisite=

Fixes #8309.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2018-05-22 12:19:27 +02:00 committed by Lennart Poettering
parent 83bf6b6741
commit 706a3df4be

View file

@ -590,10 +590,12 @@
<varlistentry> <varlistentry>
<term><varname>Requisite=</varname></term> <term><varname>Requisite=</varname></term>
<listitem><para>Similar to <varname>Requires=</varname>. <listitem><para>Similar to <varname>Requires=</varname>. However, if the units listed here
However, if the units listed here are not started already, are not started already, they will not be started and the starting of this unit will fail
they will not be started and the transaction will fail immediately. <varname>Requisite=</varname> does not imply an ordering dependency, even if
immediately.</para> 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 <para>When <varname>Requisite=b.service</varname> is used on
<filename>a.service</filename>, this dependency will show as <filename>a.service</filename>, this dependency will show as