<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ulimit on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ulimit/</link>
    <description>Recent content in Ulimit on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 21 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/ulimit/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Too Many Open Files in 2026: ulimit, systemd Limits and Kernel Tuning Explained</title>
      <link>https://www.pistack.xyz/posts/2026-11-21-too-many-open-files-ulimit-systemd-limits-tuning/</link>
      <pubDate>Sat, 21 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-21-too-many-open-files-ulimit-systemd-limits-tuning/</guid>
      <description>&lt;p&gt;The error arrives at the worst possible moment: &lt;code&gt;accept() failed (24: Too many open files)&lt;/code&gt; in nginx, &lt;code&gt;OSError: [Errno 24] Too many open files&lt;/code&gt; in a Python worker, or a Postgres backend that dies with &lt;code&gt;could not open file&lt;/code&gt;. You raise &lt;code&gt;ulimit -n&lt;/code&gt; in your shell, restart the service… and nothing changes. That is because &lt;strong&gt;&lt;code&gt;ulimit&lt;/code&gt; was never the setting that mattered&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
