2 ms·
Are you talking about `NetworkManager.service`? It has a 600s timeout. You can reduce that if you want it to fail faster. But that doesn't seem like a problem
by godelski 2y ago
Are you talking about `NetworkManager.service`?
It has a 600s timeout. You can reduce that if you want it to fail faster. But that doesn't seem like a problem with systemd, that seems like a problem with your network connection.
> If you live outside of the very default Ubuntu instance and such.
I use Arch btw
- egorfine 2y agoI'm not sure which of the turds (NetworkManager, netplan) are currently installed with ubuntu and what's their relationship with systemd but I equally hate them all. My ubuntu initiation script includes apt-get install ifupdown, which actually works unlike those two. And why bother learning because by the next ubuntu release the upcoming fanboys will replace the network stack by whatever they think they like - again. But the bug we are discussing is probably systemd's, because the network is up and running while systemd still waits for it.