The first time you start ntpd it looks for ntp.drift file which contains information about your clock frequency. If it doesn't find this file it will go into a measuring mode for about 15 minutes and then it will adjust the time. Other thing is that whenever ntp finds that your clock is set forward it will not just set it to correct time but it will sort of 'drag' the clock until it matches the correct time which also takes a while.
I can run the test tomorrow but can you clarify one thing for me. Let's say I start two JBT instances on two computers that have perfectly synchronized clocks. Will both data files be mostly identical even though forward-test on the second instance was started 0.5 seconds after the first one? On Aug 20, 3:39 pm, Eugene Kononov <[email protected]> wrote: > Oh, now I see the effect. My clock has been synced, it just took a few > minutes. Please send me your ntp.conf anyway. > > On Thu, Aug 20, 2009 at 4:36 PM, Eugene Kononov > <[email protected]>wrote: > > > ecthx, can I take a look at your ntp.conf file? I simulated the clock drift > > by setting my PC clock 10 seconds back, and NTP doesn't seem to do anything > > about it, so I assume I am missing something in the configuration. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en -~----------~----~----~----~------~----~------~--~---
