[systemd-bugs] [Bug 86488] swap + nofail = timeout and dependency failed

[bugzilla-daemon at freedesktop.org]

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

Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |NOTABUG

--- Comment #1 from Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> ---
Feature, more than a bug...

The timeout is necessary because of event-based boot. Traditionally sysvinit
would try swapon at some "random" point, which almost always worked because
bootup was slow enough for devices to show up. With systemd this is different,
because it is often faster than device discovery so it must pick some explicit
timeout and actually wait.

As for the warning: systemd.mount(5) only says that the boot will be continued.
But it is still expected that the device will be there, it just is not
important enough to stop boot without it.

I'll close this, since I don't think there's much we can do here: in some
applications it would be nicer to be quieter, in other cases it would nicer to
be more verbose, so we're never going to fit all cases. I think the current
approach strikes a good balance.

-- 
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/20141124/9e3cbb30/attachment.html>