cryptsetup-generator: use remote-cryptsetup.target when _netdev is present

This allows such devices to depend on the network. Their startup will
be delayed similarly to network mount units.

Fixes #4642.

1 files changed, 13 insertions, 0 deletions

diff --git a/man/crypttab.xml b/man/crypttab.xml
index 5223e16664..ac7d55271c 100644
--- a/man/crypttab.xml
+++ b/man/crypttab.xml
@@ -192,6 +192,19 @@
       </varlistentry>
 
       <varlistentry>
+        <term><option>_netdev</option></term>
+
+        <listitem><para>Marks this cryptsetup device as requiring network. It will be
+        started after the network is available, similarly to
+        <citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
+        units marked with <option>_netdev</option>. The service unit to set up this device
+        will be ordered between <filename>remote-cryptsetup-pre.target</filename> and
+        <filename>remote-cryptsetup.target</filename>, instead of
+        <filename>cryptsetup-pre.target</filename> and
+        <filename>cryptsetup.target</filename>.</para></listitem>
+      </varlistentry>
+
+      <varlistentry>
         <term><option>noauto</option></term>
 
         <listitem><para>This device will not be automatically unlocked