<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Leap-Second on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/leap-second/</link>
    <description>Recent content in Leap-Second on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 13 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/leap-second/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted NTP Leap Second Handling: chrony vs NTPsec vs OpenNTPD</title>
      <link>https://www.pistack.xyz/posts/2026-05-13-self-hosted-ntp-leap-second-handling-chrony-ntpsec-openntpd-guide/</link>
      <pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-13-self-hosted-ntp-leap-second-handling-chrony-ntpsec-openntpd-guide/</guid>
      <description>&lt;p&gt;When the International Earth Rotation and Reference Systems Service (IERS) announces a leap second, every NTP server on the internet must handle it correctly. The choice of NTP daemon determines whether your systems experience time jumps, clock smearing, or complete service disruption. This guide compares how &lt;strong&gt;chrony&lt;/strong&gt;, &lt;strong&gt;NTPsec&lt;/strong&gt;, and &lt;strong&gt;OpenNTPD&lt;/strong&gt; handle leap second events — a critical consideration for financial trading platforms, distributed databases, and any infrastructure where time continuity matters.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
