this post was submitted on 07 Oct 2023
789 points (98.1% liked)
Linux
48035 readers
954 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You can use
systemd-analyze blame
if 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-chain
Any 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.