ntpdate manpage is inconsistent about threshold
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ntp (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
from `man ntpdate`:
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 sim‐
ply step the time by calling the system settimeofday() routine. If the error is less than 0.5 seconds, it will slew the time by call‐
ing 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.
but later on:
-B Force the time to always be slewed using the adjtime() system call, even if the measured offset is greater than +-128 ms. The
time. the host should not be used to synchronize clients.
Is the true value 0.128 s or 0.5 s?
Changed in ntp (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Confirmed |