Re: Unable to disable SysRq

2020-11-17 Thread Matthew Miller
On Tue, Nov 17, 2020 at 04:08:19PM +0100, Vitaly Zaitsev via devel wrote: > That's why all user-space "OOM killers" must have the following > lines in their .service files: > > DynamicUser=true > AmbientCapabilities=CAP_KILL CAP_IPC_LOCK > ProtectSystem=strict > ProtectHome=true > > I think FESCo

Re: Unable to disable SysRq

2020-11-17 Thread Vitaly Zaitsev via devel
On 17.11.2020 13:26, Robert Marcano via devel wrote: User d9k on IRC found the culprit. It is low-memory-monitor. The latest commit [1] for it tries to not mess with the value with 1 is set, but it should not mess with it ever. That's why all user-space "OOM killers" must have the following li

Re: Unable to disable SysRq

2020-11-17 Thread Robert Marcano via devel
On 11/17/20 8:26 AM, Robert Marcano wrote: User d9k on IRC found the culprit. It is low-memory-monitor. The latest commit [1] for it tries to not mess with the value with 1 is set, but it should not mess with it ever. The same documentation on that commit references [2] where it says: Note

Re: Unable to disable SysRq

2020-11-17 Thread Chuck Anderson
On Tue, Nov 17, 2020 at 01:10:02PM +0100, Kevin Kofler via devel wrote: > Robert Marcano via devel wrote: > > Two times in a week I have killed all processes trying to use Alt+i. Ts > > is to easy to press the Alt and the PrtScr at the same, starting that > > way the SysRq i command. > > > > So be

Re: Unable to disable SysRq

2020-11-17 Thread Robert Marcano via devel
On 11/16/20 8:25 PM, Robert Marcano wrote: I am using a ThinkPad with one of these keyboards where the PrtScr key is between the right Alt and Ctrl, an awful position. Two times in a week I have killed all processes trying to use Alt+i. Ts is to easy to press the Alt and the PrtScr at the same

Re: Unable to disable SysRq

2020-11-17 Thread Kevin Kofler via devel
Robert Marcano via devel wrote: > Two times in a week I have killed all processes trying to use Alt+i. Ts > is to easy to press the Alt and the PrtScr at the same, starting that > way the SysRq i command. > > So before staring to write a kernel patch to add an option where the > SysRq is only trig

Re: Unable to disable SysRq

2020-11-17 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Nov 16, 2020 at 11:35:41PM -0800, Samuel Sieb wrote: > On 11/16/20 4:25 PM, Robert Marcano via devel wrote: > >My Fedora 33 kernel.sysrq value is 80, the default at > >/usr/lib/sysctl.d/50-default.conf say that it should be 16. > > > >Created /etc/sysctl.d/99-local.conf with kernel.sysrq=0,

Re: Unable to disable SysRq

2020-11-16 Thread Samuel Sieb
On 11/16/20 4:25 PM, Robert Marcano via devel wrote: My Fedora 33 kernel.sysrq value is 80, the default at /usr/lib/sysctl.d/50-default.conf say that it should be 16. Created /etc/sysctl.d/99-local.conf with kernel.sysrq=0, but after boot the value is 64, only after a single user mode boot the

Unable to disable SysRq

2020-11-16 Thread Robert Marcano via devel
I am using a ThinkPad with one of these keyboards where the PrtScr key is between the right Alt and Ctrl, an awful position. Two times in a week I have killed all processes trying to use Alt+i. Ts is to easy to press the Alt and the PrtScr at the same, starting that way the SysRq i command.