5 ms·
Step One of most disaster plans is not to create a second emergency.
by TylerE 10mo ago
Step One of most disaster plans is not to create a second emergency.
- amelius 10mo agoBut can't NTP server downtime cause a disaster?
- Vosporos 10mo agoOne (amongst many) NTP server going down creates less issues than an NTP server spreading wrong time.
- macintux 10mo agoGeneral rule of thumb: a misbehaving/slow server in any well-architected distributed system is vastly worse than a dead server.
- xeonmc 10mo agoi.e. a gaslighting husband is vastly worse than a dead husband.
- PunchyHamster 10mo agotechnically if you have 3 or more sources that would be caught; NTP protocol was designed for that eventuality
- da_chicken 10mo agoSure, 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.
- throw0101c 10mo ago> 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.
- ufocia 10mo agoYour probably meant trilaterate.
- idiotsecant 10mo agoIf your application is so critical that NTP timing loss causes disaster and your holdover fails in less than a day and you aren't generating your own via gps, you are incompetent, full stop
- geerlingguy 10mo agoAnd if things are that critical, you might have other references besides just GPS...
- throw0101c 10mo agoE.g., * https://www.meinbergglobal.com/english/products/ https://www.meinbergglobal.com/english/products/
- ronjakoi 10mo agoOr even just a microsecond emergency.
- f5129cac 10mo agoBravo