zvisha
commented
10 years ago We update the date from 1.1.2000 to X.X.2014. Thats more then 0.5 seconds )
On Sat, Mar 22, 2014 at 12:27 AM, SyRenity notifications@github.com wrote:
Appears as using immediate jump in time, rather then gradual.
Should be using the following mode:
"Time adjustments are made by ntpdate in one of two ways. If ntpdate determines the clock is in error more than 0.5 second it will simply step the time by calling the system settimeofday() routine. If the error is less than 0.5 seconds, it will slew the time by calling the system adjtime() routine. The latter technique is less disruptive and more accurate when the error is small, and works quite well when ntpdate is run by cron every hour or two."
Reply to this email directly or view it on GitHubhttps://github.com/Spondoolies-Tech/minepeon/issues/18 .
SyRenity
Appears as using immediate jump in time, rather then gradual.
Should be using the following mode:
"Time adjustments are made by ntpdate in one of two ways. If ntpdate determines the clock is in error more than 0.5 second it will simply step the time by calling the system settimeofday() routine. If the error is less than 0.5 seconds, it will slew the time by calling the system adjtime() routine. The latter technique is less disruptive and more accurate when the error is small, and works quite well when ntpdate is run by cron every hour or two."