>This can be even worse than that: the timestamp from a GPS source can take several tens of seconds to stabilize, depending on the accuracy of your GPS system and available satellites. Until then, the system date can jump back and forth around the actual time.
Ew. That's pretty bad indeed.
Forward clock jumps aren't much of a problem, software is generally
resilient to that; but *backward* clock jumps are the devil. They can
mess up log sequentiality properties; they can make software
unresponsive;
they can introduce errors in file access/modification times; etc.
Basically no important operation should be performed on a system until
we know that the system clock isn't going to jump backwards. I don't
know
how existing GPS-based systems manage that.
--
Laurent
Received on Fri Jul 21 2023 - 01:57:24 CEST