[systemd-bugs] [Bug 54210] nofail option in /etc/crypttab has no effect

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=54210

--- Comment #2 from seschwar at googlemail.com ---
On 2012-09-26 at 20:57 +0000 Matthew Monaco <dgbaley27 at 0x01b.net> wrote:
> It looks like "nofail" applies to cryptsetup.target. So while
> your device failed, cryptsetup.target succeeded without it.

I had missed that.  With the nofail option the status of
cryptsetup.target is "active" and without it it is "inactive
(dead)".  However in both cases the boot process is the same.
systemd waits until the device times out and then continues
booting normally.

> It seems like what you want to do is reduce the timeout for
> dev/disk/by/uuid/e3c24abf-143a-4d84-92b1-113f02a49a16.device

How do I do that?  The timeout option described in
man:crypttab(5) is for the timeout of the password prompt
and not of the device.  Is there something like fstab's
x-systemd.device-timeout for crypttab?

Moreover I think that crypttab's manual page suggests that the
nofail already implies an immediate timeout:

> The system will not wait for the device to show up (...)

As I see it this is a mismatch between the documentation and the
implementation and probably the source of my confusion.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20120929/41f2d6e6/attachment.html>