| |||||||||||||
|
| |||||||||||||
Shortening the ropeShortening the ropePosted Apr 7, 2009 13:34 UTC (Tue) by hmh (subscriber, #3838)In reply to: Shortening the rope by SLi Parent article: Shortening the rope
Properly done SAK should done by the kernel, for it to have a chance of being somewhat secure. It doesn't have to, nor should it be "integrated" to anything: that goes completely against what SAK is supposed to do.
What one should do is to make sure the kernel will select the correct crap for killing, and that it resets the VT (and the keyboard translation mode, damn PeeCee legacy crap) to something that can work with getty for when X doesn't come back up. And to have init or another process supervisor bring gdm/kdm back to life.
For all I know, it even already does the above :-) I should try it one of these days.
(Log in to post comments)
Shortening the rope Posted Apr 19, 2009 9:44 UTC (Sun) by TRS-80 (subscriber, #1804) [Link] With GDM at least, the SAK kills the child gdm process on the terminal, but not the parent daemon, which then spawns a new child that starts X. I tested this yesterday, as I needed to restart X to get back the 1.5GB of RAM mozilla had leaked into it. Keyboard-wise X should be using the same translation as the VT thanks to input-hotplug, not that there's a getty on that VT.
|
|
||||||||||||