<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Procfs on Nalar</title>
    <link>https://nalar.dev/tags/procfs/</link>
    <description>Recent content in Procfs on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/procfs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Diagnosing File Descriptor Leaks on Linux with procfs</title>
      <link>https://nalar.dev/diagnosing-file-descriptor-leaks-on-linux-with-procfs/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/diagnosing-file-descriptor-leaks-on-linux-with-procfs/</guid>
      <description>&lt;p&gt;A Linux process uses file descriptors for more than ordinary files. Network sockets, pipes, event descriptors, terminals, and many other kernel objects appear through the same integer-based interface.&lt;/p&gt;&#xA;&lt;p&gt;When a service slowly accumulates descriptors, it may eventually fail with &lt;code&gt;Too many open files&lt;/code&gt;, stop accepting connections, or behave unpredictably under load. Linux procfs provides enough information to investigate many descriptor leaks without installing extra tools.&lt;/p&gt;&#xA;&lt;h2 id=&#34;start-by-counting-descriptors&#34;&gt;Start by counting descriptors&lt;/h2&gt;&#xA;&lt;p&gt;For a known process ID:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
