Systemd 248 RC3: systemd-oomd is now considered fully supported

Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by garaetjjte on Sunday March 14, 2021 @10:13AM (#26455611)

>In Linux hitting a thrash situation will freeze the computer to the point where Ctrl-Alt-F2 will not switch the vterm even when waiting several minutes, and it has to be rebooted.

You can recover system from this state by manually triggering OOM killer using Magic SysRq keys. (Alt+SysRq+F, provided you have SysRq enabled in /proc/sys/kernel/sysrq)

[ Parent | on HN ]

Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by bscphil on Sunday March 14, 2021 @05:54PM (#26459688)

Is there a version of this that works on typical laptop keyboards that don't have SysRq? I could map an unused key to it with xmodmap of course, but if my X server isn't responding I don't think that would help very much!

[ Parent | on HN ]

Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by garaetjjte on Sunday March 14, 2021 @06:23PM (#26459993)

SysRq is PrintScreen, I think it should be present even on laptops?

[ Parent | on HN ]

Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by bscphil on Sunday March 14, 2021 @06:36PM (#26460148)

Oh! News to me, I definitely have it. Thanks!

[ Parent | on HN ]

Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by lolc on Sunday March 14, 2021 @11:01AM (#26455959)

This is very useful! I have to look up this combination every other month when one of my systems starts thrashing.

[ Parent | on HN ]