wabe wrote: > Neil Bothwick <n...@digimed.co.uk> wrote: > >> On Thu, 27 Apr 2017 16:56:00 -0500, Dale wrote: >> >>> One thing about alt sysreq, once you get to a certain point, you >>> have to go "all the way" with it. I've found that just the R and E >>> generally gets things back to a point it is accessible and I don't >>> have to go through it all. I think once you get to the I or S, >>> it's all or nothing at that point. Even after the E, you may have >>> to start/restart some init processes. FYI, I'm pretty sure the S >>> is what syncs the file systems and the U unmounts everything. Of >>> course, the B reboots. I can't recall what the others do exactly. >> R resets the keyboard. E sends a SIGTERM to all processes except PID1, >> which is why you need to restart services after pressing it. I sends a >> SIGKILL similarly. As you say S syncs ass filesystems, U unmounts >> filesystems and remounts them readonly and B reboots. >> >> Once you have got to E, you need to restart stuff. You may get away >> with switching runlevels to bring up all your services, or you may >> decide that once the system has got itself into a state that has you >> reaching for SysRq, a reboot is in order. > Most of the keys are documented here: > > https://wiki.ubuntuusers.de/Magic_SysRQ/ > > And even more in the kernel directory at Documentation/sysrq.txt. > > I will pin these synopsis onto the backside of my monitor. :-) > > -- > Regards > wabe
I have it on a small post-it-note stuck on the side of my monitor. I'm not sure, may have been Neil or Alan, that posted it this way. Reboot Even If System Utterly Broken. That sort of stuck with me. Still, I look at the sticky note to be sure. I found it on linuxhowtos.org which ironically, was translated from a site in your language I think. lol Anyway, it's handy to have around, just in case, and a little safety is needed when it seems the Sun just went dark. I wish I had that when I did the hal thing. Let's not go to far into that tho. Dale :-) :-)
