10 ms·
Haven't noticed this. This looks like a bug more than a fundamental issue.
by jraph 1y ago
Haven't noticed this. This looks like a bug more than a fundamental issue.
- egorfine 1y agoMy feeling is that this is not exactly a bug but rather an obscure side effect of systemd being non-transparent.
- ongy 1y agoThe default hook systemd uses to wait for network is documented in https://www.freedesktop.org/software/systemd/man/latest/systemd-networkd-wait-online.service.html https://www.freedesktop.org/software/systemd/man/latest/syst... It has the slightly odd behavior with trying to get all configured links up. This can lead to some unexpected behavior when there's more than one. But yea, the upstream stance is essentially "don't rely on network to be up before you start. That's bad software. You have to deal with network going down and back up in practice either way." Which is often not super useful.
- egorfine 1y ago> is documented in Yeah, did not help. > trying to get all configured links up Extremely helpful when some are explicitly disabled. So maybe there is a bit of a bug there, who knows. > don't rely on network to be up before you start Yeah that's the correct way.