<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Process-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/process-management/</link>
    <description>Recent content in Process-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 29 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/process-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Service Restart Detection: needrestart vs checkrestart vs debsums</title>
      <link>https://www.pistack.xyz/posts/2026-05-29-self-hosted-linux-service-restart-detection-needrestart-checkrestart-debsums-guide/</link>
      <pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-29-self-hosted-linux-service-restart-detection-needrestart-checkrestart-debsums-guide/</guid>
      <description>&lt;p&gt;After installing package updates on a Debian or Ubuntu server, some running services continue using old library code until they are restarted. This is one of the most common reasons why &amp;ldquo;patched&amp;rdquo; servers remain vulnerable — the security fix was installed, but the running process never loaded the updated binary. This guide compares three tools for detecting which services need restarting after package updates: &lt;strong&gt;needrestart&lt;/strong&gt;, &lt;strong&gt;checkrestart&lt;/strong&gt; (from debian-goodies), and &lt;strong&gt;debsums&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosted Container Init Processes: tini vs dumb-init vs docker-init for Signal Handling (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-22-container-init-processes-tini-dumb-init-docker-init-signal-handling-guide/</link>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-22-container-init-processes-tini-dumb-init-docker-init-signal-handling-guide/</guid>
      <description>&lt;p&gt;Every container runs with PID 1 as its first process. This init process has a critical responsibility that most developers overlook: &lt;strong&gt;signal handling and zombie process reaping&lt;/strong&gt;. Using the wrong PID 1 process leads to containers that ignore shutdown signals, accumulate zombie processes, and refuse to stop gracefully. This guide compares three init process solutions: &lt;strong&gt;tini&lt;/strong&gt;, &lt;strong&gt;dumb-init&lt;/strong&gt;, and &lt;strong&gt;docker-init&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosted Super-Server: systemd Socket Activation vs xinetd vs s6-networking</title>
      <link>https://www.pistack.xyz/posts/2026-05-22-self-hosted-super-server-systemd-socket-xinetd-s6-networking-guide/</link>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-22-self-hosted-super-server-systemd-socket-xinetd-s6-networking-guide/</guid>
      <description>&lt;p&gt;A super-server (also called an internet superserver) listens on multiple network ports and spawns the appropriate service daemon when a connection arrives. Instead of running dozens of services that each consume memory waiting for connections, a super-server centralizes port listening and launches services on demand.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
