r1 - 2004-11-25 - 15:40:00 - ParkerJonesYou are here: NTP >  Support Web > WebOrder > KnownHardwareIssues > ManualCalibration
NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to being used in distributed denial-of-service (DDoS) attacks. Please also take this opportunity to defeat denial-of-service attacks by implementing Ingress and Egress filtering through BCP38.

ntp-4.2.8p11 was released on 27 February 2018. It addresses 2 low-/medium-, 1 informational-/medium-, and 2 low-severity security issues in ntpd, 1 medium-severity security issue in ntpq, and provides over 65 non-security bugfixes and other improvements over 4.2.8p10.

Please see the NTP Security Notice for vulnerability and mitigation details.

Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.

Manual Calibration without NTP

This section describes how to calibrate the clock to an accuracy of order tenths of a second. This procedure was found useful when ntpd was used on a variable speed processor and upset the drift correction.


The aim is to calibrate the kernel frequency adjustment variable(s) stored in /etc/adjtime. This following is a translation of Laurent Picouleau's page. Many thanks to Mike Cook for the above explanation and supplying this link.

The following steps are to be done as root.

  • Day 1
    • Set the CMOS clock to "approximately" UTC using the BIOS (1).
    • Install hwclock and adjtimex
    • Run hwclock --set --date="MM/DD/YY hh:mm:00" --utc (2) --debug on the fourth beep (radio, I presume) (3)
  • Day 2
    • Run hwclock --set --date="MM/DD/YY hh:mm:00" --utc --debug
    • If the first value of the first line of /etc/adjtime is greater than 8 then
      • run adjtimex -u -c
      • record the suggested value for "tick"
      • run adjtimex -u -t suggested_value
    • Run adjtimex -u -l=/var/log/clocks.log
  • Day 7
    • Run adjtimex -u -l=/var/log/clocks.log
    • Run hwclock --set --date "MM/DD/YY hh:mm:00" --utc --debug
    • Run adjtimex -u -l=/var/log/clocks.log
    • Run hwclock --utc --hctosys
    • Run adjtimex -u -l=/var/log/clocks.log
    • Run adjtimex -u -c=22 -i=100
    • Calculate the average of the 20 values given for "freq"
    • Run adjtimex -u -f calculated_average
    • Run adjtimex -u -l=/var/log/clocks.log

Phew! Your clock system is now calibrated to your reference and will drift by about only one tenth of a second per day.


1. Or any other method

2. Note care the date format: month/day/year

3. Use local time, don't use GMT.

-- ParkerJones - 25 Nov 2004

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback