You can use systemd-analyze blame if you want raw numbers:
This command prints a list of all running units, ordered by the time they took to initialize. This information may be used to optimize boot-up times.
Good way to see if your systemd also waits 2 minutes for a network connection which already exists but it can't see it because systemd doesn't do the networking (lxc containers on proxmox in my case) lol.
In my case i masked the service because like i said, inside the lxc container there is no networking to do, it's done on the host (proxmox). Note that disabling the service in my case was not enough since it could be invoked by other services, and then you would have to wait again.
See this for further info and maybe arguments why you shouldn't do it.
You can use
systemd-analyze blameif you want raw numbers:Good way to see if your systemd also waits 2 minutes for a network connection which already exists but it can't see it because systemd doesn't do the networking (lxc containers on proxmox in my case) lol.
Also see systemd-analyze.
Also
systemd-analyze critical-chainAny way to speed this up? On my system in every boot it waits for network for 30s.
In my case i masked the service because like i said, inside the lxc container there is no networking to do, it's done on the host (proxmox). Note that disabling the service in my case was not enough since it could be invoked by other services, and then you would have to wait again.
See this for further info and maybe arguments why you shouldn't do it.
My main offender is something called updatedb.service, whatever that is.