You're viewing a single thread.
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.
Wouldn't you just set "networking" as a dependency on the unit of whatever you need started after?
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.
systemctl start serviceI love how fucking lennaert subtly changed that. Who cares that it complicates classic tools.
Does
After=not fit your use case? I was under the impression it does what you're looking for.