<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>System-Administration on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/system-administration/</link>
    <description>Recent content in System-Administration on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 27 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/system-administration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux OOM Prevention: earlyoom vs systemd-oomd vs PSI Monitors (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-27-self-hosted-linux-oom-prevention-earlyoom-systemd-oomd-psi-guide/</link>
      <pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-27-self-hosted-linux-oom-prevention-earlyoom-systemd-oomd-psi-guide/</guid>
      <description>&lt;p&gt;The Linux Out-Of-Memory (OOM) killer is a last-resort mechanism that terminates processes when the system runs out of memory. By the time it activates, your services are already degraded — swap is exhausted, page reclaim has failed, and the system may be completely unresponsive. The OOM killer&amp;rsquo;s heuristic process selection often terminates the wrong service, taking down your database while leaving memory-leaking background processes alive.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
