You are viewing a single comment's thread:
Seems like many advanced Linux users migrated to Arch.
I could install Linux on the old laptop too. It's not that old, 64bit for sure, it's i3. But I'd rather keep it as it is for now.
Yeah, looks like I might be overdoing it with daily trimming. You're the second person who said weekly (which was the default). I'll reverse it to weekly. I don't have a Nvme, just SSD.
Interesting things I discovered by running your command.
5.009s NetworkManager-wait-online.service
798ms systemd-udev-settle.service
566ms docker.service
330ms ufw.service
259ms blueman-mechanism.service
242ms dev-nvme0n1p2.device
203ms zfs-load-module.service
147ms networkd-dispatcher.service
133ms accounts-daemon.service
123ms udisks2.service
112ms ubuntu-system-adjustments.service
108ms modprobe@chromeos_pstore.service
108ms containerd.service
107ms systemd-resolved.service
89ms apparmor.service
88ms avahi-daemon.service
84ms polkit.service
82ms systemd-timesyncd.service
78ms [email protected]
77ms gpu-manager.service
76ms lightdm.service
75ms thermald.service
75ms plymouth-quit-wait.service
Not sure what NetworkManager-wait-online service is for, but 5s is a lot! It doesn't seem as much on boot. Maybe it doesn't block the boot process?
Also, I told docker not to run at startup. Should the service still run at startup?
And I deactivated Bluetooth, I don't use it as much. How come the service is still there?
Let me know if you notice anything else out of order and how to fix that.
By the way, I know you run a video encoder. Do you use the docker container or the pm2 process manager? I tried with pm2 and didn't work and now I'm using docker. The issue is I can't make it work with the universal firewall (unless I allow incoming). And if I check the status of ufw there are no special rules, just active or not - which is strange.
Thanks in advance!
For older laptops, even if you find different recommendations online, they're not all true, I tested a few of them but didn't find a better one than "antiX".
NetworkManager-wait-online.service is not a problem, it'll just wait until you have an active net connection before continuing booting. You could disable that but only if you are bothered about those 5 secs while booting.
About the Bluetooth, I think you have the bluetooth.service off or not present, that blueman-mechanism.service is another app service to manage the bluetooth, you can try "sudo systemctl disable blueman-mechanism.service", otherwise you can look for other ways how it can be disabled. About the docker.service, you probably told it not to run your docker images at startup, but the service still starts, it just wouldn't load your docker images.
You could disable it and enable it every time, but I guess better leave this alone if you plan to use it often.
I don't run and video encoder, I wanted to but it won't work on my rented vps and the laptop I have for a spare is too low specs for encoding. I'm only running nodes for the SPK network and Ragnarok.
View more