Skip to contentSkip to conversation

don't panic if /sbin/init exits or killed

PATCH Bodo Eggert 1 participant 1 message Mar 19, 2008 4 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw
Quoted 8 lines · Roland McGrath
Quoted 1 line

But panic() isn't better? It doesn't provide any useful info.

It is not misleading in the same way. It's clear that going to look at the kernel source is not the place to find the root of the problem.

Quoted 3 lines

Well, I think the generic "if we have a chance to survive, we should try to survive" rule is good.

Quoted 7 lines
Quoted 2 lines

If the boot init dies, at least the admin has a chance to figure out what has happened, and -o remount,ro /.

For me and you, I agree. I think the common case is that there is no admin prepared to do any such thing, but just someone expecting a reboot to fix things and preferring that a failing system reboot itself in the middle of the night rather than wedge.

I think the common case is repairing a system using init=/bin/sh, and forgetting to not log out instead of fscking the filesystem after the panic. Rebooting on panic= is fine, but not skipping the umount/sync stages.