Steve Kostecke wrote:
ntpd can normally keep your clock well within 10 ms of WAN (e.g. Internet) time servers, 5 ms of a LAN time server, and 0.01 ms of a direcly connected GPS ref-clock. Assuming that all of your time sources are ultimately synced to UTC the differences between them will be well within the slew/step threshold and your application won't notice a change in "sys_peer" (i.e. the time source you are "synced" to).
Of course, if he hasn't either got the replacement server configured, or has the authentication in place to allow it to be added on the fly, the biggest hit to the time will be that from stopping and starting ntpd, to change the configuration.
Steve has put "synced" in quotes, because ntpd actually syncs to a composite time from all the good servers, but needs to nominate one as the figurehead server.
_______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
