Public bug reported:
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?
** Affects: friendly-recovery (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1459475
Title:
friendly-recovery slows down boot time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1459475/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
