this post was submitted on 31 Jul 2026
666 points (98.5% liked)

linuxmemes

32316 readers
1094 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 3 years ago
    MODERATORS
    zephyr@lemmy.world
    rtxn@lemmy.world
    666
    The other side of Linux shutdown (lemmy.world)
    submitted 2 days ago* (last edited 2 days ago) by deathmetal27@lemmy.world to c/linuxmemes@lemmy.world
    126 comments fedilink hide all child comments
     

    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)"

    you are viewing a single comment's thread
    view the rest of the comments
    [–] lambisio@feddit.cl 2 points 1 day ago* (last edited 1 day ago) (3 children)

    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 1 points 1 day ago (2 children)

    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.cl 2 points 1 day ago (1 children)

    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.

    [–] jj4211@lemmy.world 1 points 21 hours ago

    Depends on how the network services are designed/configured.

    If the service is allowed to just bind '::', then generally, sure, start it up and more proper networking bringup can happen asynchronously.

    But folks often have it bind a specific address/interface, in which case those binds will error and cause the service to error because it was asked to bind to something it could not. This is the use case I think the online target is designed to take the race conditions out of. It's not that the service is not really useful without networking, it's that the service will exit with error if the networking isn't exactly as expected.

    Of course, in this world of genericizing things around the worst cases, they end up blocking everything just in case, because they have no idea of the user has done something like make the service only work through one interface.