<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Crash-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/crash-management/</link>
    <description>Recent content in Crash-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/crash-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Coredump Management: systemd-coredump vs ABRT vs minicoredumper (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-22-self-hosted-linux-coredump-management-systemd-abrt-minicoredumper-guide/</link>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-22-self-hosted-linux-coredump-management-systemd-abrt-minicoredumper-guide/</guid>
      <description>&lt;p&gt;When a Linux process crashes, the kernel can generate a &lt;strong&gt;coredump&lt;/strong&gt; — a snapshot of the process memory, registers, and execution state at the moment of failure. These files are essential for post-mortem debugging, but managing them at scale across servers is a challenge. Without proper coredump handling, crashes are silent, debug information is lost, and production issues remain unresolved.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
