<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Oom on *scratch*</title>
    <link>https://www.scrivano.org/tags/oom/</link>
    <description>Recent content in Oom on *scratch*</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 06 Jun 2026 10:03:54 +0000</lastBuildDate>
    <atom:link href="https://www.scrivano.org/tags/oom/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cgroup v2 OOM group</title>
      <link>https://www.scrivano.org/posts/2020-08-14-oom-group/</link>
      <pubDate>Fri, 14 Aug 2020 19:49:32 +0200</pubDate>
      <guid>https://www.scrivano.org/posts/2020-08-14-oom-group/</guid>
      <description>&lt;p&gt;One annoying issue with setting a memory limit for a container is that the OOM killer can leave the container in an inconsistent state with only some of its processes terminated. When a cgroup hits its memory limit, the kernel selects a single process to kill based on a badness score, not all the processes in the cgroup. This means that a multi-process container — for example, one running a web server and several worker processes — may continue running in a broken state after the OOM event rather than being cleanly torn down.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
