Josselin Mouette <joss@debian.org> writes: > Le mardi 14 mai 2013 à 15:28 +0800, Thomas Goirand a écrit : >> On 05/13/2013 06:05 AM, Josselin Mouette wrote: >> > Having a rock-stable PID 1 is nice and all, but it doesn’t help you if >> > something important crashes. On a production server, if apache crashes >> > and fails to reload properly because the scripts don’t get the ordering >> > right, it doesn’t help you that init is still running fine. >> >> That is quite not truth. Let's say you have a broken HDD, and that you >> forgot to setup grub on the 2nd HDD or something else that will prevent >> boot up. In one case, you're totally screwed, on the other, you just >> restart Apache ! > > Yes of course, because a different init system will magically make your > other disk bootable. Erm, no that's not what he was saying. He was assuming that there must be a fault somewhere, so if it's not in the init scripts, it must be in systemd -- this of course is nonsense, but if you start from that assumption then it is better for apache to fail to restart than it is for systemd to crash. He missed the fact that you were contrasting one non-crashing init, that is capable of restarting dead services, with another non-crashing init setup that is not able to do so (without help). Just thought I'd clear that up. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] http://www.hands.com/ |-| HANDS.COM Ltd. http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND
Attachment:
pgpE0HD7HTQEL.pgp
Description: PGP signature