Re: SysRq behavior
On Mon, 11 Dec 2000, James Simmons wrote: > > > When built into the Kernel, by only pressing the > > > PrintScreen/SysRq the current application is terminated (tested > > > on a console and GNU screen). Is this just me or I should > > > expect it? Well this should happen even when sysrq is NOT compiled into the kernel... > > Probably bug. Happens for me, too, and it is pretty nasty. Not a bug - just an easy-to-disable "feature" - read on ;) > Just played with this bug. It doesn't kill a login shell but does any > app running on it. I just went looking for where "Quit" is printed > out. When I press SysRq Quit is printed on the command line. Any ideas? Well that "print-screen" key is usually bound to ^\ : % dumpkeys | grep 'e 99' keycode 99 = Control_backslash control alt keycode 99 = Meta_Control_backslash Now by default ^\ is bound to sigquit - and should be as quite a few programs depend on that... % dumpkeys | grep [^_]Control_backslash keycode 5 = four degree dollar Control_backslash Control_backslash altgr control keycode 12 = Control_backslash control keycode 43 = Control_backslash keycode 99 = Control_backslash Looks like there're quite a few ways to generate ^\ - so disabling one of them won't hurt: % echo 'keycode 99 = VoidSymbol' | loadkeys (Note that this leaves all the "modified" versions of sysrq to do whatever they were already doing - so shift-printscreen will still generate ^\) In any case putting that somewhere in your bootup scripts should solve it ;) (or even users' login scripts as Linux allows anyone to screw up the keyboard mappings - why?!) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: SysRq behavior
Hi! > > Just played with this bug. It doesn't kill a login shell but does any > > app running on it. I just went looking for where "Quit" is printed > > out. When I press SysRq Quit is printed on the command line. Any ideas? > > Not a bug. Normally,. PrtSc will generate a ^\, which is the default > value of stty quit. Try > > stty quit ^A > cat > > and hit PrtSc Okay, perhaps then it is bad for PrtSc to generate such dangerous combination by default. Still bug ;-). Pavel -- I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: SysRq behavior
James Simmons <[EMAIL PROTECTED]> writes: > Just played with this bug. It doesn't kill a login shell but does any > app running on it. I just went looking for where "Quit" is printed > out. When I press SysRq Quit is printed on the command line. Any ideas? Not a bug. Normally,. PrtSc will generate a ^\, which is the default value of stty quit. Try stty quit ^A cat and hit PrtSc -- Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors! If you have to think twice about it, you're wrong. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: SysRq behavior
> Hi! > > > I don't remember having the same problem months (6?) ago when > > I built my first Kernel with this enabled (well, maybe I never > > touched the key). > > > > When built into the Kernel, by only pressing the > > PrintScreen/SysRq the current application is terminated (tested > > on a console and GNU screen). Is this just me or I should > > expect it? > > Probably bug. Happens for me, too, and it is pretty nasty. Just played with this bug. It doesn't kill a login shell but does any app running on it. I just went looking for where "Quit" is printed out. When I press SysRq Quit is printed on the command line. Any ideas? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: SysRq behavior
Hi! > I don't remember having the same problem months (6?) ago when > I built my first Kernel with this enabled (well, maybe I never > touched the key). > > When built into the Kernel, by only pressing the > PrintScreen/SysRq the current application is terminated (tested > on a console and GNU screen). Is this just me or I should > expect it? Probably bug. Happens for me, too, and it is pretty nasty. Pavel -- I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/