<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Time-Sync on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/time-sync/</link>
    <description>Recent content in Time-Sync on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/time-sync/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Chrony vs NTPsec vs OpenNTPD: Self-Hosted NTP Server Comparison 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-02-chrony-vs-ntpsec-vs-openntpd-self-hosted-ntp-server-guide/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-02-chrony-vs-ntpsec-vs-openntpd-self-hosted-ntp-server-guide/</guid>
      <description>&lt;p&gt;Accurate time synchronization is the foundation of distributed systems, certificate validation, log correlation, and financial transactions. Running your own NTP (Network Time Protocol) server reduces dependency on external services, improves accuracy within your network, and eliminates a potential attack vector. This guide compares three self-hosted NTP server implementations: &lt;strong&gt;Chrony&lt;/strong&gt;, &lt;strong&gt;NTPsec&lt;/strong&gt;, and &lt;strong&gt;OpenNTPD&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
