2 ms·

As a neutral party, one thing I'll say about systemd is at least they understand what a dependency is. I still haven't figured out why the upstart people think

As a neutral party, one thing I'll say about systemd is at least they understand what a dependency is. I still haven't figured out why the upstart people think it's a good idea for a service to magically start just because its dependencies are fulfilled. Maybe they think system services are like proteins or something.

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 ago
  Wow, that's disgusting.
- ibotty 11y ago
  That's wrong. Read about it at https://wiki.freedesktop.org/www/Software/systemd/NetworkTarget/ https://wiki.freedesktop.org/www/Software/systemd/NetworkTar...
  - scurvy 11y ago
    So 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