this post was submitted on 10 Sep 2023
19 points (100.0% liked)

Linux

7806 readers
160 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
 

It takes my PC (which should be fast enough; Ryzen 9, NVME) running OpenSUSE TW 42 seconds to boot, more than 30 seconds longer than before. Does anyone know what could cause the 38-second discrepancy between network.target and systemd-user-sessions.service? Is there a way to gather more information about what steps happen in between?

Posted image as text:

graphical.target @1min 42.681s
└─display-manager.service @1min 42.084s +597ms
  └─systemd-user-sessions.service @1min 42.059s +22ms
    └─network.target @4.014s
      └─NetworkManager.service @2.546s +1.466s
        └─network-pre.target @2.546s
          └─wpa_supplicant.service @4.012s +33ms
            └─dbus.service @2.054s +42ms
              └─basic.target @2.049s
                └─sockets.target @2.049s
                  └─cockpit.socket @2.036s +12ms
                    └─sysinit.target @2.003s
                      └─systemd-update-utmp.service @1.966s +36ms
                        └─auditd.service @1.939s +26ms
                          └─systemd-tmpfiles-setup.service @1.750s +162ms
                            └─systemd-journal-flush.service @1.008s +691ms
                              └─var.mount @999ms +6ms
                                └─local-fs-pre.target @992ms
                                  └─systemd-tmpfiles-setup-dev.service @829ms +79ms
                                    └─kmod-static-nodes.service @399ms +209ms
                                      └─systemd-journald.socket
                                        └─system.slice
                                          └─-.slice

EDIT: It was waiting for a network mount with a device that wasn't online anymore.

top 7 comments
sorted by: hot top controversial new old
[–] [email protected] 16 points 1 year ago

Services waiting for the year of the Linux desktop.

[–] [email protected] 12 points 1 year ago

You can see exactly what it waits for by removing "rhgb quiet" from grub_cmdline_linux and grub2 mkconfig. But usually it'll be like "Network Manager wait online" or something dumb.

[–] [email protected] 11 points 1 year ago (1 children)

my best guess, dhcp waiting trying acquired ip

[–] [email protected] 3 points 1 year ago

I have statically assigned the IP of my PC, could that be the reason?

[–] [email protected] 7 points 1 year ago (1 children)

What program are you using to get that in command line?

[–] [email protected] 7 points 1 year ago (1 children)

systemd-analyze critical-chain

[–] [email protected] 3 points 1 year ago