this post was submitted on 26 Jun 2023
584 points (98.0% liked)

linuxmemes

21225 readers
97 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 members of the community for any reason.
  • 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 will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 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. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith
    zephyr
    rtxn
    584
    deez nuts (lemmy.world)
    submitted 1 year ago by Linuxmemed to c/linuxmemes
    31 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] phx 6 points 1 year ago (1 children)

    Wouldn't you just set "networking" as a dependency on the unit of whatever you need started after?

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

    That's what you would do with the init scripts, as that environment waits until the previous one is finished. (ie you know you have working network) Systemd is in a hurry and there 'after' seems to mean 'not before' instead of 'after <specified> is finished', so after networking is started it advances to the next in line.

    [–] phx 1 points 1 year ago

    Yeah. I'm not sure what the issue there is though?

    If you're having issues with stuff that's coming up after devices but before getting an IP, you might want to try putting another service as a dependency (dhcp client service maybe).

    You may also be falling victim to interface "allow-hotplug" setting. IIRC one of my systems I had to change this in the interfaces configuration to ensure the interface was up fully before other stuff started.