On 7/18/21 7:38 AM, John Mellor wrote:
Here is the top of the current systemd-analyse blame output: $ systemd-analyze blame 27.625s plymouth-quit-wait.service 21.726s udisks2.service 13.932s libvirtd.service 13.711s systemd-journal-flush.service
OK, here's where the trouble probably lies. If memory serves, the first one can be disabled and masked safely, and if not, I'm sure somebody will correct me. I don't know about the others, but others on the list should. However, if you're not using lvm2, any services dealing with it are redundant and should be killed as a waste of boot time.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
