<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hardware-Clock on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/hardware-clock/</link>
    <description>Recent content in Hardware-Clock on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/hardware-clock/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Hardware Clock (RTC) Management: hwclock vs chrony vs systemd-timesyncd</title>
      <link>https://www.pistack.xyz/posts/2026-05-25-linux-hardware-clock-rtc-management-hwclock-chrony-systemd-timesyncd-guide/</link>
      <pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-25-linux-hardware-clock-rtc-management-hwclock-chrony-systemd-timesyncd-guide/</guid>
      <description>&lt;p&gt;Managing accurate time on Linux servers requires synchronizing both the system clock and the hardware real-time clock (RTC). While NTP daemons handle network time synchronization, the hardware clock persists across reboots and power cycles. Choosing the right tool for RTC management is critical for servers that need reliable timekeeping, audit logging compliance, and consistent timestamps across distributed systems.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
