348: OK OOMer

Today we make nice with a killer, an early out-of-memory daemon, and one of the new features in Fedora 32. We put EarlyOOM to the test in a real-world workload and are shocked by the results.

Plus we debate if OpenWrt is still the best router solution, and chew on Microsoft's new SELinux competitor.

Special Guests: Alex Kretzschmar and Neal Gompa.

Support LINUX Unplugged

Links:

• Window Maker Version 0.95.9 Released
  
• Microsoft announces IPE, a new code integrity feature for Linux — Microsoft says that IPE is not intended for general-purpose computing. The IPE LSM was designed for very specific use cases where security is paramount, and administrators need to be in full control of what runs on their systems. Examples include embedded systems, such as network firewall devices running in a data center, or Linux servers running strict and immutable configurations and applications.
• OpenWrt - Opkg susceptible to MITM
  
• Brent sits down with Daniel Foré, founder of elementary OS
  
• Know when we're going to be live. Check out the calendar!
  
• Keep the conversation going join us on Telegram
  
• Fedora nightly compose finder
  
• Fedora 32 Looking At Using EarlyOOM By Default To Better Deal With Low Memory Situations — The oom-killer generally has a bad reputation among Linux users. This may be part of the reason Linux invokes it only when it has absolutely no other choice. It will swap out the desktop environment, drop the whole page cache and empty every buffer before it will ultimately kill a process. At least that's what I think that it will do. I have yet to be patient enough to wait for it, sitting in front of an unresponsive system.
  
• earlyoom - Early OOM Daemon for Linux — The oom-killer generally has a bad reputation among Linux users. This may be part of the reason Linux invokes it only when it has absolutely no other choice. It will swap out the desktop environment, drop the whole page cache and empty every buffer before it will ultimately kill a process. At least that's what I think that it will do. I have yet to be patient enough to wait for it, sitting in front of an unresponsive system.
  
• rfjakob/systembus-notify: systembus-notify - system bus notification daemon
  
• oomd — Out of memory killing has historically happened inside kernel space. On a memory overcommitted linux system, malloc(2) and friends usually never fail. However, if an application dereferences the returned pointer and the system has run out of physical memory, the linux kernel is forced to take extreme measures, up to and including killing processes. This is sometimes a slow and painful process because the kernel can spend an unbounded amount of time swapping in and out pages and evicting the page cache. Furthermore, configuring policy is not very flexible while being somewhat complicated.
• low-memory-monitor on GitLab
  
• low-memory-monitor — low-memory-monitor, as its name implies, monitors the amount of free physical memory on the system and will shoot off signals to interested user-space applications, usually session managers, or sandboxing helpers, when that memory runs low, making it possible for applications to shrink their memory footprints before it's too late either to recover a usable system, or avoid taking a performance hit.
  
• Nohang — Nohang is a highly configurable daemon for Linux which is able to correctly prevent out of memory (OOM) and keep system responsiveness in low memory conditions.

• Better interactivity in low-memory situations - devel - Fedora Mailing-Lists
  
• EnableEarlyoom - Fedora Project Wiki
  
• Nushell - The Unix philosophy of shells, where pipes connect simple commands together, and bring it to the modern style of development.
  
• Timekpr - simple and easy to use time managing software that helps optimizing time spent at computer.