Quote:
Originally Posted by Cactus Chef
Well when you decide to use a distro whose whole raison d'être is that they don't like systemd, you have to assume the risk that at some point it will become stale/irrelevant. It's a knee-jerk reaction to some initial change that often smooths out over time until it's no longer needed.
|
That's my fear about jumping ship. But it isn't knee-jerk -- or not just knee-jerk. systemd is an actual problem for me and my job. NFS mounts being one already noted. NIS is another service that systemd tries to start before the network is up.
Worse still, wrapping a "is the network up" test in a systemd unit file doesn't work: for example, if you try to ping the network gateway within a unit and it "fails" because the interfaces are still negotiating with the switches, systemd treats it as a unit failure and kills the whole unit. The only thing that works mostly consistently is to sleep 2-3 minutes and then start the service -- which defeats systemd's promise of faster boot times.
Never mind that shaving seconds off of boot times is meaningless when servers take 5-10 minutes to POST before they even get to the OS boot process.