<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Socket-Activation on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/socket-activation/</link>
    <description>Recent content in Socket-Activation 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/socket-activation/index.xml" rel="self" type="application/rss+xml" />
    <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>
