ntpdate manpage is inconsistent about threshold

Bug #830277 reported by Max Rabkin
6
This bug affects 1 person
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
              default is to step the time using settimeofday() if the offset is greater than +-128 ms. Note that, if the offset is much
              greater than +-128 ms in this case, that it can take a long time (hours) to slew the clock to the correct value. During this
              time. the host should not be used to synchronize clients.

Is the true value 0.128 s or 0.5 s?

Dave Walker (davewalker)
Changed in ntp (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.