4 ms·
This is just a personal anecdote, but so far systemd is the only init system ever to fail to reboot by first stopping all services it could (including sshd!) an
by clarry 10y ago
This is just a personal anecdote, but so far systemd is the only init system ever to fail to reboot by first stopping all services it could (including sshd!) and then get infinitely stuck waiting on one problematic service. In the 12 years I've used Linux and OpenBSD, no other init systme ever did something like that.
What a nightmare that was to debug and fix.
I'll be happy to go with a system with fewer moving parts, even if that means reboots take a minute longer.
- lomnakkus 10y agoJust curious, but was it really infinite? I think there's a weird default of waiting something like 5 minutes for certain services to stop...? (You could have also hit the infamous NFS unmount bug which is basically just a kernel fuck-up.)
- Mister_Snuggles 10y agoWhile I don't think this was related to the init system, I have had a Linux box completely hang while trying to reboot it because an NFS server that it was connected to went away. I'm pretty sure this was an infinite hang as it sat like that for over five days before I could physically get to it to hit the power button. Hanging during reboot is something that, IMO, should never happen.
- lomnakkus 10y agoYup, I'm guessing NFS too (see my sibling reply). In my anecdotal experience that's the _only_ case where systemd has failed to reboot, and it's not exactly systemd's fault that the kernel just hangs indefinitely.