178
submitted 6 months ago by stepan@lemmy.cafe to c/linuxmemes@lemmy.world

Not exactly as funny meme as I would like it to be, but I just found out about that feature after having to hold the power button due to a frozen system countless times, and I had to tell someone.

all 24 comments
sorted by: hot top controversial new old
[-] eager_eagle@lemmy.world 31 points 6 months ago

Related and IMO a much better option for Linux desktops:

Early OOM

[-] boredsquirrel@slrpnk.net 12 points 6 months ago* (last edited 6 months ago)

This is great! Why doesnt distros use this by default???

Just put plasmashell and a few in there and you will have a working oom killer. Finally.

I will install this the first thing tomorrow

Wait... Fedora has this since quite a while, strange.

[-] mexicancartel@lemmy.dbzer0.com 6 points 6 months ago

Because if i'm rendering on blender on my lower end PC with expected freezes but it auto kills the render?

[-] Brickardo@feddit.nl -1 points 6 months ago

Sounds like niche use cases

[-] mexicancartel@lemmy.dbzer0.com 6 points 6 months ago

Not niche there can be times when you want to run something heavy and it auto kills the exact thing you are trying to run. You have a 1gb ram device and it kills everything? Thats undesirable

[-] boredsquirrel@slrpnk.net 1 points 6 months ago

Hm.... the process itself should not take that much RAM. I dont know if normally the OS should assign the max RAM to the program.

But this should not happen and I wonder how "just letting it freeze" works

[-] Ptsf@lemmy.world 1 points 6 months ago

We do not break userspace in this household young man.

[-] MonkderDritte@feddit.de 4 points 6 months ago* (last edited 6 months ago)

Why doesnt distros use this by default???

Nohang has some explanations to this.

I.e. kernel devs are ignorant to the issue of oomkiller not working as intended on desktop.

Edit: Lkml is down.

[-] marcos@lemmy.world 2 points 6 months ago

Just decrease your swap space.

Unless you have an unusual system, there's no reason to have several GB of swap.

[-] eager_eagle@lemmy.world 7 points 6 months ago

that won't solve the system unresponsiveness

[-] marcos@lemmy.world 0 points 6 months ago

Have you tried?

Because it does.

[-] eager_eagle@lemmy.world 10 points 6 months ago

yes, even turning swap off entirely doesn't solve it. It doesn't take much to find people reporting a similar experience.

[-] MonkderDritte@feddit.de 1 points 6 months ago* (last edited 6 months ago)

Better enable swap again. Linux expects swap.

[-] vox@sopuli.xyz 2 points 6 months ago

or fiddle with the vm/swappiness value

[-] dan@upvote.au 1 points 6 months ago* (last edited 6 months ago)
[-] MonkderDritte@feddit.de 2 points 6 months ago* (last edited 6 months ago)

Wasn't oomd the facebook thing for complicated server setups?

edit: yeah, for large data centers. Imho overengineered for single user desktop sessions. Earlyoom is simple and tiny.

[-] CraigeryTheKid@lemm.ee 17 points 6 months ago

ok... I'll ask.. where the heck is the "sysreq" key on my standard keyboard?

[-] julianh@lemm.ee 8 points 6 months ago

Should be the screenshot key

[-] CraigeryTheKid@lemm.ee 6 points 6 months ago

so it is! and I tested it, of course, with alt-sys-b which instantly rebooted my machine. nice.

[-] CarlosCheddar@lemmy.world 7 points 6 months ago

How come sysreq + f is not on by default? After discovering and enabling it I haven’t had to hard restart due to hangs or crashes.

[-] stepan@lemmy.cafe 10 points 6 months ago

Debian has it by default I think. Arch has it disabled because it might be a security risk if someone had physical access to your computer.

[-] lurch@sh.itjust.works 9 points 6 months ago

those debian daredevils like the thrill of living on the edge

[-] toynbee@lemmy.world 0 points 6 months ago

Raising Skinny Elephants Is Utterly Boring ... Or so I've heard.

this post was submitted on 23 May 2024
178 points (97.3% liked)

linuxmemes

21281 readers
180 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS