           SPELL=ntp
         VERSION=stable-4.2.0a-20060127
          SOURCE=$SPELL-$VERSION.tar.gz
SOURCE_DIRECTORY=$BUILD_DIRECTORY/$SPELL-$VERSION
   SOURCE_URL[0]=http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/snapshots/ntp-stable/2006/01/$SOURCE
     SOURCE_HASH='sha512:d7462fd69950dbec43dfd146715418c9bacce67c2afa200fc3a658613e0da484062dc1f563fca880e40ec72ce74b84745a9b7288b0a80407c98291ed4aad4791'
        WEB_SITE=http://www.ntp.org/
         ENTERED=20011004
         UPDATED=20050224
#         GCC_VERSION=3.4
      LICENSE[0]=PD
       BUILD_API=2
            DOCS="$DOCS README.* WHERE-TO-START *.y2kfixes"
           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
