Consistent Issues Over Years With Linux SOLVED



Here is the output for Debian 10 Buster Mate:
systemd-analyze blame
11.725s apt-daily.service
7.909s man-db.service
7.332s ifupdown-pre.service
3.638s NetworkManager.service
3.210s udisks2.service
3.142s dev-sda1.device
3.128s ModemManager.service
2.136s alsa-restore.service
2.125s apparmor.service
2.069s accounts-daemon.service
1.571s bluetooth.service
1.570s avahi-daemon.service
1.566s wpa_supplicant.service
1.565s rsyslog.service
1.564s pppd-dns.service
1.300s logrotate.service
1.169s systemd-logind.service
723ms systemd-udevd.service
619ms networking.service
529ms systemd-rfkill.service
511ms lightdm.service
508ms plymouth-quit-wait.service
350ms dev-disk-by\x2duuid-9cf94bb0\x2d42fa\x2d4b87\x2d943d\x2d48aac22
 
I'll run systemd-analyze blame on all 3 distro's tomorrow. It's late.

I really don't want to go back to Slackware as it is not the easiest distro to run and it doesn't do dependency resolution.
Yes it does
You would have dependency checking in slack if you added slapt-get and gslapt.
For slackware I use a few approaches slpkg is one of them.
 
Here is the output for Linux Mint 19.3 XFCE:

$ systemd-analyze blame
22.052s apt-daily.service
5.103s qemu-kvm.service
408ms systemd-logind.service
392ms apt-daily-upgrade.service
342ms lightdm.service
341ms plymouth-quit-wait.service
293ms vboxdrv.service
239ms systemd-rfkill.service
195ms dev-nvme0n1p2.device
195ms udisks2.service
123ms snapd.service
82ms systemd-journal-flush.service
77ms NetworkManager.service
68ms ufw.service
60ms ubuntu-system-adjustments.service
60ms networkd-dispatcher.service
58ms systemd-udev-trigger.service
55ms upower.service
53ms systemd-journald.service
53ms networking.service
51ms keyboard-setup.service
44ms systemd-resolved.service
37ms accounts-daemon.service
 
wow. My systemd analyse is a LOT bigger (is that bragging?)
But seriously my systemd starts over 80 processes and still starts in a bout 15seconds or so.

6.148s NetworkManager-wait-online.service
4.327s systemd-udev-settle.service
3.261s lvm2-monitor.service
2.762s dracut-initqueue.service
1.648s lvm2-pvscan@259:3.service
1.220s upower.service
880ms udisks2.service
852ms akmods.service
739ms plymouth-quit-wait.service
706ms firewalld.service
553ms systemd-logind.service
401ms sssd.service
302ms systemd-rfkill.service
282ms initrd-switch-root.service
270ms systemd-homed.service
238ms systemd-udevd.service
233ms polkit.service
194ms lightdm.service
166ms systemd-journald.service
155ms systemd-journal-flush.service
155ms systemd-userdbd.service
135ms httpd.service
121ms abrtd.service
121ms plymouth-read-write.service
121ms dnf-makecache.service
117ms libvirtd.service
117ms ModemManager.service
113ms cups.service
110ms auditd.service
95ms php-fpm.service
87ms initrd-parse-etc.service
79ms systemd-remount-fs.service
72ms [email protected]
71ms sysroot.mount
68ms smartd.service
55ms systemd-udev-trigger.service
53ms cockpit-motd.service
47ms boot.mount
41ms sysstat-summary.service
37ms deepin-accounts-daemon.service
34ms systemd-vconsole-setup.service
34ms colord.service
32ms home2.mount
32ms systemd-fsck@dev-disk-by\x2duuid-C96C\x2d4CB4.service
32ms systemd-tmpfiles-clean.service
31ms dracut-cmdline.service
29ms systemd-modules-load.service
29ms dbus-broker.service
29ms var-lib-nfs-rpc_pipefs.mount
24ms chronyd.service
23ms [email protected]
23ms bluetooth.service
22ms accounts-daemon.service
22ms NetworkManager.service
21ms avahi-daemon.service
21ms unbound-anchor.service
21ms lm_sensors.service
20ms dracut-pre-pivot.service
20ms rsyslog.service
19ms dev-mapper-fedora\x2dswap.swap
18ms sshd.service
17ms plymouth-switch-root.service
16ms boot-efi.mount
16ms systemd-tmpfiles-setup-dev.service
16ms gssproxy.service
16ms cockpit.socket
15ms systemd-binfmt.service
15ms sysstat.service
13ms systemd-tmpfiles-setup.service
12ms netcf-transaction.service
12ms plymouth-start.service
11ms dmraid-activation.service
10ms import-state.service
10ms dracut-pre-udev.service
10ms systemd-fsck-root.service
9ms rtkit-daemon.service
8ms initrd-cleanup.service
8ms systemd-repart.service
8ms dev-hugepages.mount
7ms proc-sys-fs-binfmt_misc.mount
7ms systemd-update-utmp-runlevel.service
7ms dev-mqueue.mount
7ms [email protected]
7ms sys-kernel-debug.mount
6ms systemd-update-utmp.service
6ms sys-kernel-tracing.mount
6ms systemd-user-sessions.service
6ms wpa_supplicant.service
6ms kmod-static-nodes.service
6ms systemd-random-seed.service
6ms systemd-sysctl.service
5ms rpc-statd-notify.service
5ms sysstat-collect.service
5ms nfs-convert.service
4ms initrd-udevadm-cleanup-db.service
2ms iscsi-shutdown.service
1ms dracut-shutdown.service
1ms sys-fs-fuse-connections.mount
1ms tmp.mount
1ms sys-kernel-config.mount

I know there is a lot of difference between SSD and HDD.
 
Alex, hi, still playing catch up after my week of no internet :)

I note your success with the other Thread over the shutdown, goodonyer.

What is the startup time for Mint now? I have some ideas.

Wizard
 
Alex, hi, still playing catch up after my week of no internet :)

I note your success with the other Thread over the shutdown, goodonyer.

What is the startup time for Mint now? I have some ideas.

Wizard
The startup time for Mint is now 1 minute and 30 seconds.
 
The startup time for Mint is now 1 minute and 30 seconds.

Well, that's better, but not great, eh?

I'll review this Thread, put together some stuff, and come back to you next 48.

How is your arm and shoulder?

Ta (thanks) for asking. Slowly and surely getting gains, my physio bloke thinks another 8 months, but I may not get back full functionality.

Avagudweegend

Chris
 
Well, that's better, but not great, eh?

I'll review this Thread, put together some stuff, and come back to you next 48.



Ta (thanks) for asking. Slowly and surely getting gains, my physio bloke thinks another 8 months, but I may not get back full functionality.

Avagudweegend

Chris
All the best for the recovery Wiz.
 
I think I will live with 1 minute and 30 seconds.

That's much better than 3 to 5 minutes like before.
 

Members online


Top