<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Unix Domain Sockets on Nalar</title>
    <link>https://nalar.dev/tags/unix-domain-sockets/</link>
    <description>Recent content in Unix Domain Sockets on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/unix-domain-sockets/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SCM_RIGHTS Transfers Open File Descriptions Across Process Boundaries</title>
      <link>https://nalar.dev/scm-rights-transfers-open-file-descriptions-across-process-boundaries/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/scm-rights-transfers-open-file-descriptions-across-process-boundaries/</guid>
      <description>&lt;p&gt;&lt;code&gt;SCM_RIGHTS&lt;/code&gt; lets one process send a reference to an open file through a Unix domain socket. The receiver obtains a file descriptor in its own descriptor table, but the transfer does not reopen the pathname or copy the kernel object. On Linux, the resulting reference has semantics equivalent to duplicating the sender&amp;rsquo;s descriptor into the receiving process.&lt;/p&gt;&#xA;&lt;p&gt;That distinction matters whenever a process boundary is also an authority boundary. A supervisor can open a socket, file, pipe, device, or other descriptor-backed object and pass the established reference to a worker. The worker receives access to the already-open object, including open-file state that can remain shared with the sender.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
