dfoxfra...@gmail.com said: > One thing to keep in mind is that if the client is using SO_TIMESTAMP but the > server isn't, or vice versa, you're going to introduce a persistent > inaccuracy on the order of a microsecond, due to the resulting asymmetry in > the point at which the timestamp is captured.
That's another reason it's hard to notice. If both systems do it wrong, the errors cancel. Or partially cancel if their CPU speed doesn't match. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
