On Thu, Jul 27, 2017 at 08:30:12AM +0200, Richard Cochran wrote: > We trust the foreign masters based on their announce messages, and we > elect the GM based on their advertised values. Now, a buggy master > can ruin the time keeping on the slave in many ways, and we don't > second guess them. Of course, one could build in analysis and > heuristics in order to detect bad masters, but that is lots of work.
Are there other values that can break slaves in such a way they have to be restarted? > 2. The GM says either !currentUtcOffsetValid or !timeTraceable, but > the advertised offset is greater than ours. > > In this case we assume that time has gone on, and the hard coded > offset is simply out of date. Probably the GM has a more recent > idea of the correct offset. We do *not* accept smaller offsets > because this is physically impossible. Well, a large asteroid hitting the Earth could speed up the rotation so much it would require deleting leap seconds. :) -- Miroslav Lichvar ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
