Lines Matching full:interval

69 sent to its clients, so that after some predefined interval the leap second
70 offset is compensated.  The smear interval should be long enough,
80 UTC before the leap second, up to the beginning of the smear interval, and
82 finished, at the end of the smear interval.  By examining the first byte of
96 - During the smear interval the time provided by smearing NTP servers
108 certain interval, which is what we call smearing the leap second.
128 depended on the poll interval.  The system time was off by 1 second for
158 those few servers accordingly.  If the smear interval is long enough so that
164 the clients during the smear interval is as small as possible, compared to
167 particular smear interval it's easy to determine the start point of the
205 - The leap smear interval should be at least several hours' long, and up to
206 1 day (86400s).  If the interval is too short then the applied smear offset
211 interval should be configured on each server.
226 servers at the same time.  During the smear interval they would get
233 If an NTP server should perform leap smearing then the leap smear interval
239 Please keep in mind the leap smear interval should be between several and 24
245 When ntpd starts and a smear interval has been specified then a log message
248  ntpd[31120]: config: leap smear interval 86400 s
250 While ntpd is running with a leap smear interval specified the command:
268 interval all the time, while the 'leapsmearoffset' value is 0 outside the
269 interval and increases from 0 to -1000 ms over the interval.  So this can be