man: explain noauto/nofail more carefully in crypttab
https://bugzilla.redhat.com/show_bug.cgi?id=1524759
This commit is contained in:
parent
b4b36f4405
commit
5d0e48519b
|
@ -218,16 +218,23 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><option>noauto</option></term>
|
<term><option>noauto</option></term>
|
||||||
|
|
||||||
<listitem><para>This device will not be automatically unlocked
|
<listitem><para>This device will not be added to <filename>cryptsetup.target</filename>.
|
||||||
on boot.</para></listitem>
|
This means that it will not be automatically unlocked on boot, unless something else pulls
|
||||||
|
it in. In particular, if the device is used for a mount point, it'll be unlocked
|
||||||
|
automatically during boot, unless the mount point itself is also disabled with
|
||||||
|
<option>noauto</option>.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><option>nofail</option></term>
|
<term><option>nofail</option></term>
|
||||||
|
|
||||||
<listitem><para>The system will not wait for the device to
|
<listitem><para>This device will not be a hard dependency of
|
||||||
show up and be unlocked at boot, and not fail the boot if it
|
<filename>cryptsetup.target</filename>. It'll be still pulled in and started, but the system
|
||||||
does not show up.</para></listitem>
|
will not wait for the device to show up and be unlocked, and boot will not fail if this is
|
||||||
|
unsuccessful. Note that other units that depend on the unlocked device may still fail. In
|
||||||
|
particular, if the device is used for a mount point, the mount point itself is also needs to
|
||||||
|
have <option>noauto</option> option, or the boot will fail if the device is not unlocked
|
||||||
|
successfully.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
|
Loading…
Reference in a new issue