<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Service-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/service-management/</link>
    <description>Recent content in Service-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/service-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Systemd Unit Generators: Dynamic Service Management with Generators, Socket Activation, and Template Units</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-linux-systemd-generators-socket-activation-template-units/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-linux-systemd-generators-socket-activation-template-units/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;System administrators managing fleets of servers often face the same challenge: how to create and maintain systemd unit files that adapt to changing environments. Manually writing &lt;code&gt;.service&lt;/code&gt; files for every container, application instance, or mount point does not scale. Linux systemd provides three powerful mechanisms for dynamic service creation: &lt;strong&gt;systemd generators&lt;/strong&gt; (run at boot to create transient units), &lt;strong&gt;socket activation&lt;/strong&gt; (start services on-demand), and &lt;strong&gt;template units&lt;/strong&gt; (parameterized service definitions).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
