<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Process-Monitoring on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/process-monitoring/</link>
    <description>Recent content in Process-Monitoring on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/process-monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux Open File Inspection: lsof vs fuser vs /proc/PID/fd — Self-Hosted Process File Monitoring</title>
      <link>https://www.pistack.xyz/posts/2026-05-23-linux-open-file-inspection-lsof-fuser-proc-pid-fd-guide/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-23-linux-open-file-inspection-lsof-fuser-proc-pid-fd-guide/</guid>
      <description>&lt;p&gt;When a Linux server runs out of disk space due to deleted-but-still-open files, or when you need to figure out which process is holding a mount point busy during unmount, the ability to inspect which processes have which files open becomes critical. Three approaches dominate this space on Linux: &lt;strong&gt;lsof&lt;/strong&gt; (the Swiss Army knife), &lt;strong&gt;fuser&lt;/strong&gt; (the quick checker), and direct &lt;strong&gt;/proc/PID/fd&lt;/strong&gt; inspection (the kernel-native method). Each serves different operational scenarios — from quick terminal checks to automated monitoring scripts.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
