[email protected] said: >> It might be useful to make sure that any workaround for >> OS X is general enough to handle another case. > It will be. We just fall back to the old BSD adjtime(2) call, which > everybody (even OS X) has.
Thanks. That explains why/how it works and why the results are so crappy. That procedure can only slew the clock, no drift correction. The crappiness will depend on your luck and/or temperature. A crystal that happens to be more accurate will drift less between corrections. In the context of TESTFRAME, we can have 2 sets of replay files. One for systems that implement ntp_adjtime, and another set for systems using adjtime (no x). So far, only OS X and OpenBSD are in the latter category. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
