View Single Post
  #7   (View Single Post)  
Old 20th August 2009
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,977
Default

ntpd(8) makes very small clock adjustments, unless you start it with the -s parameter. Two excerpts from the man page:
Quote:
-S Do not set the time immediately at startup. This is the de-
fault.

-s Set the time immediately at startup. Allows for a large time
correction, eliminating the need to run rdate(8).
.
.
.
ntpd uses the adjtime(2) system call to correct the local system time
without causing time jumps. Adjustments of 32ms and greater are logged
using syslog(3). The threshold value is chosen to avoid having local
clock drift thrash the log files. Should ntpd be started with the -d or
-v option, all calls to adjtime(2) will be logged.

After the local clock is synchronized, ntpd adjusts the clock frequency
using the adjfreq(2) system call to compensate for systematic drift.
The "error" message says that the clocks are not (yet) synced, and that another attempt will be made in 55 minutes.

If you want instant synchronization, use -s, or, as bsdfan and the man page say, use rdate.
Reply With Quote