Messages in this thread | | | Subject | Re: SYSRQ accidents | Date | Tue, 01 Sep 1998 09:07:31 +0100 | From | David Woodhouse <> |
| |
mj@ucw.cz said: > > AFAIK, behaviour of SysRq-L did never change -- it doesn't kill the > system, it just kills all processes except for kernel threads and you > can still sync and unmount afterwards.
SysRq-L kills init. Once init is dead, the latest kernels just lock up, and don't even respond to further SysRq commands.
I've asked twice, but nobody has taken the time to explain the reasons for this change in behaviour, although there was a suggestion that it was because of the problems of assigning parents to orphaned processes when init doesn't exist. I would have thought there was an alternative solution to that, though.
---- ---- ---- David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302 Project Leader, Process Information Systems Mobile: (+44) 976 658355 Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK. finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
| |