<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Timekeeping on Nalar</title>
    <link>https://nalar.dev/tags/timekeeping/</link>
    <description>Recent content in Timekeeping on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 22 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/timekeeping/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TFD_TIMER_CANCEL_ON_SET Reports Realtime Clock Discontinuities</title>
      <link>https://nalar.dev/timerfd-cancel-on-set-reports-realtime-clock-discontinuities/</link>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/timerfd-cancel-on-set-reports-realtime-clock-discontinuities/</guid>
      <description>&lt;p&gt;A &lt;code&gt;timerfd&lt;/code&gt; armed against wall-clock time can cross a discontinuous clock adjustment before its deadline. With &lt;code&gt;TFD_TIMER_CANCEL_ON_SET&lt;/code&gt;, Linux exposes that event through the descriptor: a subsequent &lt;code&gt;read()&lt;/code&gt; fails with &lt;code&gt;ECANCELED&lt;/code&gt; rather than presenting the clock jump as an ordinary timer expiration.&lt;/p&gt;&#xA;&lt;p&gt;The flag is deliberately narrow. It applies only when &lt;code&gt;timerfd_settime()&lt;/code&gt; arms an absolute timer on &lt;code&gt;CLOCK_REALTIME&lt;/code&gt; or &lt;code&gt;CLOCK_REALTIME_ALARM&lt;/code&gt;, and it changes the handling of discontinuous changes to those clocks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
