My plymouth remains using too much loadtime...
I´m trying to reduce my TOO LONG boottime... I went from 1min 16sec. down to 1min 1sec. by disabling a lot of services which I don´t use.
I also disabled: plymouth.quit.wait.service
But then when I write: systemd-analyze blame, it shows plymouth.quit.wait.service(even after I disabled it...)
When I write: systemctl status plymouth.quit.wait.service, then it says: No such file or directory. Inactive(dead)
That makes no sense to me!
Isnt it possible to disable plymouth service ?
Thank in advanced
35.803s plymouth-quit-wait.service
10.716s firewalld.service
8.297s dev-mapper-fedora\x2droot.device
7.880s systemd-udev-settle.service
5.767s systemd-journal-flush.service
5.319s accounts-daemon.service
4.633s libvirtd.service
3.533s abrtd.service
2.873s lvm2-monitor.service
2.573s ModemManager.service
2.232s gssproxy.service
2.212s systemd-fsck-root.service
2.169s polkit.service
2.047s proc-fs-nfsd.mount
1.927s systemd-fsck@dev-disk-by\x2duuid-cf634048\x2da20a\x2d47bb\x2dba
1.903s chronyd.service
1.863s packagekit.service
1.821s systemd-logind.service
1.799s livesys.service
1.799s dnf-makecache.service
1.793s netcf-transaction.service
1.793s mcelog.service
1.764s fedora-readonly.service
Disable ModemManager if you are not using a modem.
Why is your firewalld taking so long?
You can also try minimizing the time systemd-journal takes. See here for problem, and here for solution
Yes, I use a modem.
I also wonder why my firewalld is taking so long...but how to find out if I use ipt ? Because otherwise I would disable my firewallld...
I don't know how to find out why your firewall is taking so long but I do know that it is not worth disabling it to save 10s during your boot. How often do you reboot? Once a day? So what do the 10 secs matter?