Filippo Valsorda  

Well that's a first for me: an NTP Pool server sent a wildly wrong time, and systemd-timesyncd jumped the system time on Trastevere first forward 0.82s and then *backwards* 0.76s.

Thankfully Sunlight failed safe, crashed (which fired alerts), and recovered once the clock caught up.

WTF?

ntppool.org/scores/2603:c020:8

1+
Elias
Follow

@filippo I remember in the old days, it was said that time was supposed to be monotonic. 🙂

Maybe chrony would have handled that incident better than systemd-timesyncd did?

· Web · 0 · 0 · 2
Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml