man: document that 'nofail' also has an effect on ordering
Prompted by #9765
This commit is contained in:
parent
27d4866ad8
commit
e6c7c7ffd5
|
@ -370,12 +370,10 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><option>nofail</option></term>
|
<term><option>nofail</option></term>
|
||||||
|
|
||||||
<listitem><para>With <option>nofail</option>, this mount will
|
<listitem><para>With <option>nofail</option>, this mount will be only wanted, not required, by
|
||||||
be only wanted, not required, by
|
<filename>local-fs.target</filename> or <filename>remote-fs.target</filename>. Moreover the mount unit is not
|
||||||
<filename>local-fs.target</filename> or
|
ordered before these target units. This means that the boot will continue without waiting for the mount unit
|
||||||
<filename>remote-fs.target</filename>. This means that the
|
and regardless whether the mount point can be mounted successfully.</para>
|
||||||
boot will continue even if this mount point is not mounted
|
|
||||||
successfully.</para>
|
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue