Transcript:

Two panel meme.

Top panel: Woman in the front seat of a car screaming at a child in the rear seat. She’s saying “Why can’t you just shutdown?”

Bottom panel: A child screaming “A stop job is running for Session c2 of user … (1:30 / no limit)”

  • Aatube@lemmy.dbzer0.com
    0·
    7 days ago

    I don’t think that’s true. Bootup and suspending don’t need stopping things like that.

    Source: I use systemd btw

    • Venia Silente@lemmy.dbzer0.comEnglish
      0·
      7 days ago

      Oh but it’s not just stopping things, starting things is subject to the same issue also:

      A start job is running for "wait for network to be available"

      (attached to a network interface that is not necessarily connected at bootup)

      Systemd is just special.

        • lambisio@feddit.clEnglish
          0·
          6 days ago

          Don’t mask or disable the systemd service.

          Edit /etc/netplan/01-netcfg.yaml and add optional: true to any devices that may not always be available.

          That’s absolutely systemd’s fault. In any Linux system the only network interface that can (more or less) always trusted to be available and complete a full initialization sequence is lo Absolutely nothing else.

          (The worse if you happen to have a WiFi that autoconnects but does it across the same SSID to different endpoints, but that one is wpa_supplicant’s fault if I’m not mistaken. Systemd just makes it worse)

          • Aatube@lemmy.dbzer0.com
            0·
            6 days ago

            It depends on whether you’re a server or PC. For PCs (as in personal computing) I agree systemd-networkd-wait-online.service should be disabled. For servers, I think it’s plausible that you require a network to be at all meaningful, especially if there’s some sort of database.

            • lambisio@feddit.clEnglish
              0·
              6 days ago

              Eh, the only kind of server that I think you absolutely need full networking (address, iptables, routing, maybe even DNS) to be “meaningful” would be a database replica. Anything else, there is full use to partial network configuration: anything small enough that lets in a network connection someone else can use to diagnose (eg.: you can have a server that can spin up a meaningful session with only address and netmask, not routing).

              That said, I’ve never seen a server, with or without systemd, set to wait for all possible network interfaces that are present to be fully configured… would me emotional murder with something like wireguard that by necessity has a depends on another interface’s routing. Usually with just lo plus any one available interface, it tends to suffice.