summaryrefslogtreecommitdiffstats
path: root/utils/ntp/DETAILS
blob: d9778b8f1bdb213f6ca7167125252ee3f8b90e62 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
           SPELL=ntp
         VERSION=4.2.4p7
  SECURITY_PATCH=1
     SOURCE_HASH=sha512:d08368c9bd146461c2337f27af596d79f9a7a9294ed66f91a4b66a40c020e5e2e2f0c2d2481920d24fd89acaef110149f1e00c8cb27c93b496960b17fcf94dd3
          SOURCE=$SPELL-$VERSION.tar.gz
SOURCE_DIRECTORY=$BUILD_DIRECTORY/$SPELL-$VERSION
   SOURCE_URL[0]=ftp://ftp.udel.edu/pub/ntp/ntp4/$SOURCE
   SOURCE_URL[1]=http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/$SOURCE
        WEB_SITE=http://www.ntp.org/
         ENTERED=20011004
      LICENSE[0]=PD
            DOCS="$DOCS README.* WHERE-TO-START *.y2kfixes"
        KEYWORDS="utils"
           SHORT="Sync your time with an ntp server"
cat << EOF
NTP (Network Time Protocol) tries to keep servers in sync

Very usefull with GPS timesources, but typically used in a third
level setup to your ISP (Which typicall syncs to a first level timesource)

Several methods, use "ntpd -g -q ntp.server.dom" in a crontab
(or after connecting), or create /etc/ntp.conf and start "ntpd -g"

The -g is needed to enable a big step, otherwise it takes too long to sync.

Note: issue the "ntpd -g" command ASAP after the network is initialized,
and check out ntp-wait to not have it take too long to sync in why other
server's starts (and their logs get bad).
It's fastest slew rate is 0.5ms/sec, ie. 2000 secs to fix a secon
EOF