archer65
Utente Attivo
- Messaggi
- 1,327
- Reazioni
- 121
- Punteggio
- 70
Sono 3 giorni che cambio continuamente distribuzione sperando di trovarne una che davvero mi convinca...e l'ho trovata!
Fedora Gnome:bevuta:
Tema Arc+Evopop Icon
Fresca di installazione, ma ci sono dei piccoli dubbi:
Perchè ci mette così tanto????
Fedora Gnome:bevuta:
Tema Arc+Evopop Icon
Fresca di installazione, ma ci sono dei piccoli dubbi:
systemd-analyzeStartup finished in 2.835s (kernel) + 4.900s (initrd) + 1min 33.713s (userspace) = 1min 41.449s
systemd-analyze blame 24.845s plymouth-quit-wait.service
8.245s dev-sda1.device
7.294s systemd-journal-flush.service
6.384s firewalld.service
5.105s libvirtd.service
4.455s udisks2.service
4.346s accounts-daemon.service
4.318s systemd-udev-settle.service
4.076s jexec.service
3.852s abrtd.service
3.107s ldconfig.service
2.813s cups.service
2.621s plymouth-start.service
2.361s chronyd.service
2.288s polkit.service
2.180s proc-fs-nfsd.mount
2.145s packagekit.service
2.110s systemd-udevd.service
2.038s ModemManager.service
2.036s livesys.service
2.030s gssproxy.service
2.005s lvm2-monitor.service
1.788s systemd-tmpfiles-setup-dev.service
1.712s fedora-readonly.service
1.593s rtkit-daemon.service
1.445s systemd-rfkill.service
1.265s dnf-makecache.service
1.149s systemd-random-seed.service
848ms systemd-sysusers.service
769ms avahi-daemon.service
684ms systemd-journald.service
680ms dev-mqueue.mount
655ms gdm.service
620ms user@42.service
616ms bluetooth.service
603ms NetworkManager.service
595ms iio-sensor-proxy.service
537ms wpa_supplicant.service
533ms abrt-ccpp.service
476ms systemd-logind.service
450ms tmp.mount
449ms systemd-remount-fs.service
443ms auditd.service
441ms systemd-vconsole-setup.service
440ms systemd-backlight@backlight:acpi_video0.service
437ms proc-sys-fs-binfmt_misc.mount
417ms dev-disk-by\x2duuid-827477c8\x2df24c\x2d4538\x2d8d22\x2d6539c90
407ms fedora-import-state.service
406ms dev-hugepages.mount
371ms systemd-fsck@dev-disk-by\x2duuid-63bd3f4e\x2dba5f\x2d481f\x2d8b
325ms systemd-hwdb-update.service
314ms upower.service
287ms systemd-udev-trigger.service
272ms plymouth-read-write.service
235ms systemd-tmpfiles-setup.service
231ms systemd-journal-catalog-update.service
230ms colord.service
200ms user@1000.service
199ms rpc-statd-notify.service
177ms systemd-sysctl.service
175ms dracut-shutdown.service
153ms systemd-fsck-root.service
134ms dmraid-activation.service
133ms kmod-static-nodes.service
108ms systemd-update-utmp-runlevel.service
100ms systemd-update-done.service
92ms nfs-config.service
88ms home.mount
52ms blk-availability.service
52ms systemd-user-sessions.service
31ms systemd-update-utmp.service
19ms livesys-late.service
14ms sys-kernel-config.mount
13ms sys-kernel-debug.mount
13ms sys-fs-fuse-connections.mount
5ms var-lib-nfs-rpc_pipefs.mount
systemd-analyze critical-chain
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 @1min 33.598s
└─multi-user.target @1min 33.598s
└─libvirtd.service @23.893s +5.105s
└─remote-fs.target @23.845s
└─remote-fs-pre.target @23.845s
└─iscsi-shutdown.service @23.837s
└─network.target @23.828s
└─wpa_supplicant.service @25.848s +537ms
└─dbus.service @14.825s
└─basic.target @14.785s
└─sockets.target @14.785s
└─iscsid.socket @14.785s
└─sysinit.target @14.760s
└─sys-fs-fuse-connections.mount @57.417s +13ms
└─system.slice
└─-.slice
Perchè ci mette così tanto????