Bonjour à tous,
Je suis avec un xubuntu 18.04 sur un ordi assez récent. Je met plus d'une minute à démarrer, sachant qu'il n'ya pas grand chose dessus. Je voulais savoir s'il y avait moyen d'accélérer? J'ai déjà fait deux trois manips trouvées sur les forums (notament masker le networkManager wait service, qui m'a fait gagner 10 secondes). J'ai fait également des manips sur le journal flux. Maintenant, j'ai ça:
sylves@sylves-X510UAR:~$ systemd-analyze
Startup finished in 4.885s (firmware) + 4.305s (loader) + 4.332s (kernel) + 36.911s (userspace) = 50.435s
graphical.target reached after 36.890s in userspace
sylves@sylves-X510UAR:~$ systemd-analyze blame
sylves@sylves-X510UAR:~$ systemd-analyze blame
24.066s dev-sda2.device
20.695s systemd-tmpfiles-setup-dev.service
15.583s systemd-sysctl.service
8.139s snapd.service
5.234s keyboard-setup.service
5.105s systemd-modules-load.service
4.550s networkd-dispatcher.service
4.078s NetworkManager.service
3.791s thermald.service
3.113s udisks2.service
3.112s wpa_supplicant.service
2.376s grub-common.service
2.029s accounts-daemon.service
1.914s systemd-journal-flush.service
1.428s dev-loop0.device
1.342s dev-loop7.device
1.327s speech-dispatcher.service
1.325s lm-sensors.service
1.323s bluetooth.service
1.312s rsyslog.service
1.260s ModemManager.service
1.254s avahi-daemon.service
1.250s dev-loop1.device
1.228s gpu-manager.service
1.189s dev-loop10.device
1.123s systemd-random-seed.service
1.081s dev-loop8.device
1.061s dev-loop2.device
1.033s apport.service
1.032s dev-loop5.device
1.029s dev-loop3.device
1.028s dev-loop4.device
999ms dev-loop6.device
962ms dev-loop9.device
925ms systemd-udevd.service
920ms dev-loop11.device
816ms systemd-logind.service
749ms lightdm.service
745ms plymouth-quit-wait.service
717ms swapfile.swap
690ms colord.service
583ms upower.service
476ms snap-gtk\x2dcommon\x2dthemes-1353.mount
443ms apparmor.service
437ms snap-core18-1144.mount
389ms snap-inkscape-5874.mount
377ms systemd-journald.service
361ms systemd-remount-fs.service
349ms snap-core18-1192.mount
323ms hddtemp.service
280ms snap-inkscape-4693.mount
228ms systemd-timesyncd.service
228ms systemd-resolved.service
222ms snap-vlc-1049.mount
185ms systemd-update-utmp.service
179ms snap-gtk2\x2dcommon\x2dthemes-5.mount
173ms polkit.service
163ms kmod-static-nodes.service
160ms qemu-kvm.service
138ms setvtrgb.service
137ms systemd-tmpfiles-setup.service
131ms plymouth-read-write.service
123ms user@1000.service
120ms systemd-fsck@dev-disk-by\x2duuid-4F15\x2d0186.service
117ms snap-core-7713.mount
117ms plymouth-start.service
116ms dev-hugepages.mount
116ms dev-mqueue.mount
115ms sys-kernel-debug.mount
100ms boot-efi.mount
96ms snap-core-7917.mount
91ms snap-vlc-770.mount
85ms snap-gtk\x2dcommon\x2dthemes-1313.mount
51ms systemd-udev-trigger.service
51ms snap-pdftk-9.mount
31ms systemd-rfkill.service
31ms snapd.seeded.service
20ms snapd.socket
14ms ufw.service
8ms kerneloops.service
6ms alsa-restore.service
5ms systemd-backlight@backlight:intel_backlight.service
3ms systemd-update-utmp-runlevel.service
3ms systemd-user-sessions.service
3ms rtkit-daemon.service
2ms console-setup.service
1ms sys-fs-fuse-connections.mount
1ms sys-kernel-config.mount
sylves@sylves-X510UAR:~$ 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 @36.890s
└─multi-user.target @36.890s
└─snapd.seeded.service @36.858s +31ms
└─snapd.service @28.716s +8.139s
└─basic.target @28.618s
└─sockets.target @28.618s
└─snapd.socket @28.597s +20ms
└─sysinit.target @28.568s
└─apparmor.service @28.124s +443ms
└─local-fs.target @28.123s
└─boot-efi.mount @28.023s +100ms
└─systemd-fsck@dev-disk-by\x2duuid-4F15\x2d0186.service @27.
└─dev-disk-by\x2duuid-4F15\x2d0186.device @27.870s
~
~
la dernière ligne de la critical chain (dev-disk-by) me parait longue par rapport a ce que j'ai vu trainer sur le net. Il y aurait moyen de réduire? Il ya autrechose que je n'ai pas vu?
