From: Zbigniew Jędrzejewski-Szmek Date: Tue, 12 Dec 2017 19:51:24 +0000 (+0100) Subject: man: explain noauto/nofail more carefully in crypttab X-Git-Tag: v237~185^2~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5d0e48519b7160bacbfdc4d0703b2650401df588;p=thirdparty%2Fsystemd.git man: explain noauto/nofail more carefully in crypttab https://bugzilla.redhat.com/show_bug.cgi?id=1524759 --- diff --git a/man/crypttab.xml b/man/crypttab.xml index 474d3d83e01..dc43257d4ed 100644 --- a/man/crypttab.xml +++ b/man/crypttab.xml @@ -218,16 +218,23 @@ - This device will not be automatically unlocked - on boot. + This device will not be added to cryptsetup.target. + 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 + . - The system will not wait for the device to - show up and be unlocked at boot, and not fail the boot if it - does not show up. + This device will not be a hard dependency of + cryptsetup.target. It'll be still pulled in and started, but the system + 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, or the boot will fail if the device is not unlocked + successfully.