From c0ed8e717b242743ef147294f01dfb7588b98352 Mon Sep 17 00:00:00 2001
From: Xiao Pan <xyz@flylightning.xyz>
Date: Wed, 6 Nov 2024 13:32:23 -0800
Subject: pacdiff

---
 etc/chrony.conf | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/etc/chrony.conf b/etc/chrony.conf
index 32da9e04..678eed84 100644
--- a/etc/chrony.conf
+++ b/etc/chrony.conf
@@ -27,9 +27,9 @@
 # you can access at http://support.ntp.org/bin/view/Servers/WebHome or
 # you can use servers from the pool.ntp.org project.
 
-! server ntp1.example.net iburst
-! server ntp2.example.net iburst
-! server ntp3.example.net iburst
+! server 0.arch.pool.ntp.org iburst
+! server 1.arch.pool.ntp.org iburst
+! server 3.arch.pool.ntp.org iburst
 
 # I don't use auto_offline because: what if wifi connected but has no network? this seems happened a lot to me when modem is up but router is down
 # I don't use offline because: I want to sync the clock sooner
@@ -128,11 +128,11 @@ ntsdumpdir /var/lib/chrony
 
 ! pidfile /var/run/chrony/chronyd.pid
 
-# If the system timezone database is kept up to date and includes the
-# right/UTC timezone, chronyd can use it to determine the current
-# TAI-UTC offset and when will the next leap second occur.
+# The system timezone database usually comes with a list of leap seconds and
+# corresponding TAI-UTC offsets.  chronyd can use it to set the offset of the
+# system TAI clock and have an additional source of leap seconds.
 
-leapsectz right/UTC
+leapseclist /usr/share/zoneinfo/leap-seconds.list
 
 #######################################################################
 ### INITIAL CLOCK CORRECTION
-- 
cgit v1.2.3-70-g09d2