Dopo aver aggiornato il sistema con fedup alla versione 22 ho riscontrato che all’avvio ci mette tanto tempo, riporto di seguito l’output di:
[skiava@skiava]# uname -r
4.2.6-200.fc22.x86_64
[root@skiava]# systemd-analyze time
Startup finished in 988ms (kernel) + 5.253s (initrd) + 51.535s (userspace) = 57.777s
[root@skiava]# systemd-analyze blame --no-pager
35.673s plymouth-quit-wait.service
10.702s dev-mapper-fedora\x2droot.device
10.128s firewalld.service
7.375s accounts-daemon.service
6.641s ModemManager.service
6.237s systemd-udev-settle.service
4.170s lm_sensors.service
3.797s rtkit-daemon.service
3.719s abrtd.service
2.805s cups.service
2.652s systemd-journald.service
1.979s systemd-udevd.service
1.712s lvm2-monitor.service
1.582s systemd-binfmt.service
1.486s packagekit.service
1.410s fedora-readonly.service
1.311s systemd-tmpfiles-setup-dev.service
1.228s NetworkManager.service
1.225s gdm.service
1.151s plymouth-start.service
981ms abrt-ccpp.service
927ms proc-sys-fs-binfmt_misc.mount
847ms chronyd.service
846ms dmraid-activation.service
820ms udisks2.service
790ms systemd-journal-flush.service
733ms colord.service
704ms polkit.service
698ms systemd-fsck@dev-disk-by\x2duuid-3d9fb24e\x2d047c\x2d46c7\x2db45a\x2d36272f0a2720.service
682ms lvm2-pvscan@8:18.service
678ms systemd-logind.service
575ms mcelog.service
520ms netcf-transaction.service
490ms systemd-fsck@dev-mapper-fedora\x2dhome.service
462ms systemd-udev-trigger.service
402ms systemd-vconsole-setup.service
375ms systemd-tmpfiles-setup.service
363ms [email protected]
354ms systemd-tmpfiles-clean.service
346ms dev-hugepages.mount
343ms home.mount
335ms systemd-remount-fs.service
321ms systemd-sysctl.service
283ms kmod-static-nodes.service
278ms boot.mount
259ms fedora-import-state.service
240ms wpa_supplicant.service
239ms systemd-update-utmp.service
234ms tmp.mount
203ms systemd-random-seed.service
197ms [email protected]
129ms systemd-fsck-root.service
125ms upower.service
105ms dev-mapper-fedora\x2dswap.swap
99ms plymouth-read-write.service
71ms systemd-user-sessions.service
60ms sys-kernel-debug.mount
55ms auditd.service
51ms dev-mqueue.mount
44ms dracut-shutdown.service
34ms sys-fs-fuse-connections.mount
17ms systemd-update-utmp-runlevel.service
5ms sys-kernel-config.mount
[root@skiava]# systemd-analyze critical-chain --no-pager
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @51.514s
└─multi-user.target @51.511s
└─NetworkManager.service @22.014s +1.228s
└─firewalld.service @11.882s +10.128s
└─basic.target @11.639s
└─sockets.target @11.639s
└─iscsiuio.socket @11.638s
└─sysinit.target @11.569s
└─systemd-update-utmp.service @11.325s +239ms
└─auditd.service @11.262s +55ms
└─systemd-tmpfiles-setup.service @10.870s +375ms
└─fedora-import-state.service @10.607s +259ms
└─local-fs.target @10.601s
└─run-user-42.mount @20.981s
└─local-fs-pre.target @4.367s
└─systemd-tmpfiles-setup-dev.service @3.050s +1.311s
└─kmod-static-nodes.service @2.509s +283ms
└─systemd-journald.socket
└─-.slice
[root@skiava]# come mai?
