4 ms·
Someone tell that to RedHat. They consider the network "up" once the device gets link, not when the system gets an IP address. Even in environments without span
by scurvy 11y ago
Someone tell that to RedHat. They consider the network "up" once the device gets link, not when the system gets an IP address. Even in environments without spanning tree, this is a problem due to massive parallelization -- spawning 30 processes 5ms after the network is "up" but doesn't have an IP from DHCP yet.
The solution? Put a sleep 7 in there, thus making the entire process slower than the previous solution.
- crdoconnor 11y agoWow, that's disgusting.
- ibotty 11y agoThat's wrong. Read about it at https://wiki.freedesktop.org/www/Software/systemd/NetworkTarget/ https://wiki.freedesktop.org/www/Software/systemd/NetworkTar...
- scurvy 11y agoSo either I use systemd's sleep or my sleep, but either way it's broken out of the box. Great job! EDIT: RHEL/CentOS only supports NetworkManager for this. Which sucks if you don't want to run NetworkManager (for a litany of reasons). $ yum whatprovides "*/systemd-networkd-wait-online.service" No matches found