Systemd-OOMD Continues Coming Together For Better Linux Out-Of-Memory Handling

[starshipeleven]

So all things about "Linux is good go low-end machines and bla bla bla" are a completely bullshit. Good to know!

Come on...

The main reason that "linux is good in low-end machines" is that it does not need 1.5GB for itself and a GUI, not even with GNOME, unlike Windows, nor it wastes 500MB of RAM to be able to run 32bit applications in a 64bit system, unlike windows.

You don't have low-ram issues if you use less ram than what you have. Big brain move.

But when you do use that ram up, it's worse than Windows, at least until Systemd comes and saves the day, again.

[fkoehler]

Some people don't seem to realize that "Print Screen" and "SysRq" produce the same keycode, even if there's no "SysRq" label on the key.

Count me in that camp . One of the reasons might be, that Alt-PrintScreen-Whatever simply does nothing, so DAUs like me assume, that it is not the right key-combination. Nowadays, instead of doing a flush or reboot or whatever, it's new job seems to be to print:

sysrq: this sysrq operation is disabled.

which you can see only, if you have switched to a text console with Ctrl-Alt-F3 or whatever it is mapped to on your distro :-/

Honestly, is there any realistically valid justification for why this change is a great idea?

Correction: Alt-PrintScreen-b will still reboot (without syncing), Alt-PrintScreen-s will sync, but most of the other combinations are disabled, amongst them the oom-killer. Weird.

[tildearrow]

Neither did your April Fool's joke in kwin-lowlatency. I only figured it out a couple hours ago. That sucked.

It was not meant to last more than one day.

[AH88]

Correction: Alt-PrintScreen-b will still reboot (without syncing), Alt-PrintScreen-s will sync, but most of the other combinations are disabled, amongst them the oom-killer. Weird.

The full set of SysRq commands aren't enabled by default. You can enable them all by creating "/etc/sysctl.d/sysrq.conf" with the contents "kernel.sysrq = 1". Then you can use "sudo sysctl --system" to reload the config (instead of rebooting) and Alt+SysRq+F to invoke the OOM killer.

[fkoehler]

The full set of SysRq commands aren't enabled by default. You can enable them all by creating "/etc/sysctl.d/sysrq.conf" with the contents "kernel.sysrq = 1". Then you can use "sudo sysctl --system" to reload the config (instead of rebooting) and Alt+SysRq+F to invoke the OOM killer.

Thanks a lot, this goes straight into my cheatsheets. The output of "sudo sysctl --system" is actually quite instructive :-)