Re:NTP at NIST Boulder Has Lost Power
by Vosporos on Saturday December 20, 2025 @06:46AM
(#46335486)
One (amongst many) NTP server going down creates less issues than an NTP server spreading wrong time.
[ Parent
| on HN ]
Re:NTP at NIST Boulder Has Lost Power
by macintux on Saturday December 20, 2025 @06:56AM
(#46335528)
General rule of thumb: a misbehaving/slow server in any well-architected distributed system is vastly worse than a dead server.
i.e. a gaslighting husband is vastly worse than a dead husband.
Re:NTP at NIST Boulder Has Lost Power
by PunchyHamster on Saturday December 20, 2025 @07:39AM
(#46335744)
technically if you have 3 or more sources that would be caught; NTP protocol was designed for that eventuality
Re:NTP at NIST Boulder Has Lost Power
by da_chicken on Saturday December 20, 2025 @07:55AM
(#46335822)
Sure, but not needing a failure to cascade to yet another failsafe is still a good idea. After all, all software has bugs, and all networks have configuration errors.
Re:NTP at NIST Boulder Has Lost Power
by throw0101c on Saturday December 20, 2025 @09:54AM
(#46336609)
> technically if you have 3 or more sources that would be caught; NTP protocol was designed for that eventuality
Either go with one clock in your NTPd/Chrony configuration, or ≥4.
Yes, if you have 3 they can triangulate, but if one goes offline now you have 2 with no tie-breaker. If you have (at least) 4 servers, then one can go away and triangulation / sanity-checking can still occur with the 3 remaining.