<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>File-Handles on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/file-handles/</link>
    <description>Recent content in File-Handles on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 29 Jul 2026 11:21:32 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/file-handles/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming the Beast of Open File Handles and Unnecessary Service Exposure</title>
      <link>https://linuxeries.org/post/2026-07-29-taming-the-beast-of-open-file-handles-and-unn/</link>
      <pubDate>Wed, 29 Jul 2026 11:21:32 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-07-29-taming-the-beast-of-open-file-handles-and-unn/</guid>
      <description>&lt;h2 id=&#34;introduction-to-open-file-handles&#34;&gt;Introduction to Open File Handles&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when a process leaves a trail of open file handles, causing performance issues and security vulnerabilities. Open file handles are a common issue in Linux systems, and managing them is crucial to prevent problems. In this article, we&amp;rsquo;ll explore how to identify and manage open file handles, as well as tackle unnecessary service exposure.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-open-file-handles&#34;&gt;Understanding Open File Handles&lt;/h2&gt;&#xA;&lt;p&gt;When a process opens a file, the kernel assigns a unique file descriptor, which is used to interact with the file. Normally, when a process is done with a file, it closes the file descriptor, releasing system resources. However, if a process fails to close its file descriptors, open file handles can accumulate, leading to problems. The real trick is to catch these issues before they cause trouble.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
