touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Well spotted. I think we can just drop the After=systemd-udev-
settle.service. I need to think about whether we actually need it (the
upstart job called udev settle), but if so, we could just call that in
ExecStartPre= instead of Before=.

** No longer affects: systemd (Ubuntu)

** Changed in: friendly-recovery (Ubuntu)
       Status: New => Triaged

** Changed in: friendly-recovery (Ubuntu)
   Importance: Undecided => Low

** Changed in: friendly-recovery (Ubuntu)
       Status: Triaged => In Progress

** Changed in: friendly-recovery (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1459475

Title:
  friendly-recovery slows down boot time

Status in friendly-recovery package in Ubuntu:
  In Progress

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