<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>File-Locking on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/file-locking/</link>
    <description>Recent content in File-Locking on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/file-locking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>File Locking Libraries in 2026: filelock vs flock vs proper-lockfile</title>
      <link>https://www.pistack.xyz/posts/2026-09-27-file-locking-libraries-filelock-flock-proper-lockfile-comparison/</link>
      <pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-27-file-locking-libraries-filelock-flock-proper-lockfile-comparison/</guid>
      <description>&lt;p&gt;Two replicas of your self-hosted job runner wake up at 02:00. Both decide it is their turn to rebuild the nightly report. Both read the same state file, both write the same output, and by morning you have a half-written CSV plus a duplicate charge in your invoicing table. Nothing in your infrastructure was misconfigured — you simply never told the two processes that the file is a shared resource. That is a &lt;em&gt;file locking&lt;/em&gt; problem, and it is solved in application code, not by adding another container.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
