lkml.org 
[lkml]   [1998]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: SYSRQ accidents
Date
From

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

\
 
 \ /
  Last update: 2005-03-22 13:44    [W:0.053 / U:0.392 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site