2 ms·
> systemd provides you with the capability of starting a service "after network is up" so it needs to be able to tell "when network is up" That's not that hard
by makomk 12y ago
> systemd provides you with the capability of starting a service "after network is up" so it needs to be able to tell "when network is up"
That's not that hard once you have proper dependency-driven init, Gentoo's done it for a long time. You just need some way for the networking scripts to tell init that they're started now. Traditionally they'd do it by forking into the background once they're done starting just like any other init script. It's a bit harder if the network might not become available until after startup but not that much so.
- kijin 12y ago> It's a bit harder if the network might not become available until after startup but not that much so. That rarely happens in server environments. I wonder how much of the recent debates about init systems is caused by the the rise of mobile consumer devices and developers' desire to cater to them. I care when my laptop takes more than a few seconds to start up, but I really don't care when one of my cloud servers takes a few minutes to start up. Network not ready yet? Meh, we could just sleep(10) and try again.