<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Atomicity on Nalar</title>
    <link>https://nalar.dev/tags/atomicity/</link>
    <description>Recent content in Atomicity on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/atomicity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>rename Replaces a Directory Entry Atomically on Linux</title>
      <link>https://nalar.dev/rename-replaces-a-directory-entry-atomically-on-linux/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/rename-replaces-a-directory-entry-atomically-on-linux/</guid>
      <description>&lt;p&gt;A successful &lt;code&gt;rename()&lt;/code&gt; can replace an existing destination pathname without exposing an intermediate state in which that destination name is missing. Processes resolving the destination observe either the old directory entry or the replacement, subject to filesystem and mount constraints.&lt;/p&gt;&#xA;&lt;p&gt;That atomic namespace transition is narrower than several properties often associated with file replacement. It does not make prior writes durable, does not force directory metadata to stable storage, and does not invalidate file descriptors that already refer to the replaced file.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
