[Bug 1459475] Re: friendly-recovery slows down boot time

[Launchpad Bug Tracker]

This bug was fixed in the package friendly-recovery - 0.2.31

---------------
friendly-recovery (0.2.31) wily; urgency=medium

  * debian/friendly-recovery.service: Don't put this between
    systemd-udev-settle.service and systemd-fsck-root.service, to avoid
    blocking fsck'ing the root partition on udev-settle. Only call udevadm
    settle when we are actually being run. (LP: #1459475)
  * Bump Standards-Version to 3.9.6; no changes necessary.

 -- Martin Pitt <martin.pitt at ubuntu.com>  Mon, 01 Jun 2015 15:45:51
+0200

** Changed in: friendly-recovery (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to friendly-recovery in Ubuntu.
https://bugs.launchpad.net/bugs/1459475

Title:
  friendly-recovery slows down boot time

Status in friendly-recovery package in Ubuntu:
  Fix Released

Bug description:
  I noticed that systemd-fsck-root.service runs very late in my boot,
  which slows it down.  This turns out to be due to friendly-
  recovery.service being After=udev settle, and Before=systemd-fsck-
  root.service.  This causes fsck-root to wait until after udev settle,
  which takes quite some time ( which is probably another issue ), even
  though during normal boots, friendly-recovery is not run at all due to
  its Condition depending on the kernel command line recovery argument.

  Is there a way to reorganize the relationships so that the transitive
  ordering is not triggered when friendly-recovery is not run at all?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1459475/+subscriptions