Am 12.04.2017 um 07:33 schrieb Terry Barnaby:
With a 50s boot to login screen that gives:
Startup finished in 2.069s (kernel) + 3.395s (initrd) + 25.451s
(userspace) = 30.915s
12.391s systemd-journal-flush.service
8.049s lvm2-monitor.service
7.862s systemd-udev-settle.service
7.502s dev-sda5.device
6.231s packagekit.service
5.528s abrtd.service
5.030s accounts-daemon.service
4.937s boapns.service
4.245s NetworkManager.service
2.751s systemd-logind.service
...
I don't think there are any issues with this particular laptop
when a single partition (dev-sda5.device) needs 7 seconds i throw that
machine out of the window and on proper machines lvm also don't take
that long (320ms lvm2-monitor.service)
[root@rh:~]$ systemd-analyze blame
9.238s mysqld.service
3.724s smb.service
3.169s accounts-daemon.service
2.906s vmware.service
2.098s network.service
1.963s vmware-modules.service
1.960s iptables.service
1.914s cups.service
1.882s systemd-logind.service
1.867s disk-tuning.service
1.615s postfix.service
1.576s dev-md1.device
1.560s mdmonitor.service
1.560s io-scheduler.service
1.512s network-bonding.service
1.511s zram.service
1.510s systemd-user-sessions.service
1.483s rtkit-daemon.service
1.437s avahi-daemon.service
1.334s user@500.service
1.218s user@4500.service
1.205s user@0.service
1.196s user@48.service
1.035s vmware-vmnet.service
692ms polkit.service
318ms systemd-vconsole-setup.service
315ms udisks2.service
313ms
systemd-fsck@dev-disk-by\x2duuid-1de836e4\x2de97c\x2d43ee\x2db65c\x2d400b0c29d3aa.service
294ms lm_sensors.service
290ms disk-timeout.service
230ms systemd-tmpfiles-setup-dev.service
226ms fedora-readonly.service
208ms network-bonding-bridge.service
199ms systemd-udevd.service
_______________________________________________
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
