<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Prctl on Nalar</title>
    <link>https://nalar.dev/tags/prctl/</link>
    <description>Recent content in Prctl on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/prctl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PR_SET_PDEATHSIG Binds a Child Notification to Parent Thread Exit</title>
      <link>https://nalar.dev/pr-set-pdeathsig-binds-child-notification-to-parent-thread-exit/</link>
      <pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/pr-set-pdeathsig-binds-child-notification-to-parent-thread-exit/</guid>
      <description>&lt;h1 id=&#34;pr_set_pdeathsig-binds-a-child-notification-to-parent-thread-exit&#34;&gt;PR_SET_PDEATHSIG Binds a Child Notification to Parent Thread Exit&lt;/h1&gt;&#xA;&lt;p&gt;&lt;code&gt;PR_SET_PDEATHSIG&lt;/code&gt; lets a Linux process request a signal when the thread that created it terminates. The mechanism is narrow: it is a kernel-delivered notification tied to a parental relationship, not a general process-lifetime contract and not a guarantee that two processes terminate together.&lt;/p&gt;&#xA;&lt;p&gt;That distinction matters in supervisors, launchers, and helper processes. A child can react to loss of its creator without polling a PID, but the exact parent identity, setup timing, inheritance rules, and credential transitions define where the mechanism stops.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
