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:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's never been popular by anybody except RedHat, that's how they sell courses end certifications.
Still haven't found a way to start something after networking has finished when it takes a bit to set everything up. (and no, not going to limit vlans, tunnels,...)
It's a technical 'solution' for a marketing problem.
Does
After=
not fit your use case? I was under the impression it does what you're looking for.Alas, nop, After= starts a service after networking has started. Somewhere systemd assumes that starting takes x amount of time, which seems to be correct for 1 to a few interfaces, but as soon as you start messing about with vlans, pppoe over 1 vlan and tunnels over pppoe over said vlan (and that's only the outside) that assumption is incorrect.
To link services to a specific interface you need an extra BindsTo=sys-devices-virtual-net-vlan666.device when you want the service to start after vlan666 is actually up. (else it's just started after the depedency is started) Starting vlans/tunnels takes a tad of time, especially when you have 11 vlans, 2 tunnels and a pppoe interface between 1 vlan and the 2 tunnels.
Requires= seems to be for services, BindsTo= for devices.