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

linuxmemes

20757 readers
485 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith
zephyr
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
[โ€“] [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.