- Setup ntp.conf. Try to find stratum 2 servers as close (ip-wise) as
possible.
- Refrain from using stratum1 servers.
- start the xntp daemon, view /var/log/messages
- use "ntpq -c peer" to show the sync status
- set the HW-clock from time to time
I saw the ntp daemon go nuts on some systems, in this case just run
ntpdate timeserver [timeserver ..]
from crontab every other hour or so. Less nice, but works too
/etc/ntp.conf
## Outside source of synchronized time
# European Stratum 1-2
server fartein.ifi.uio.no
server err.ee.ethz.ch
server ntp.exnet.com
server ntp2a.mcc.ac.uk
server ntp1.pipex.net
# Austrian Stratum 2
server ntp.austria.eu.net
server time.cso.net
##local nodes
peer other.server.inmydmz
## Miscellaneous stuff
driftfile /etc/ntp.drift # path for drift file
logfile /var/log/ntp # alternate log file
/etc/rc.config:
START_XNTPD=yes
XNTPD_INITIAL_NTPDATE="lemon.exnet.com"
crontab
0 0 1 * * root /sbin/hwclock -w
Hope that helps
Rainer
"Eduardo J. Vega Arguedas"
On Fri, 21 Jul 2000 rhoerbe@netpromote.co.at wrote:
- Setup ntp.conf. Try to find stratum 2 servers as close (ip-wise) as possible. hmmm ... i always used just netdate ts1.unvie.ac.at ts2.univie.ac.at (or any other timeservers) and run this from crontab every night ...
Don't think that this solution isn't good enough... greets Markus Gaugusch _____________________________ Markus Gaugusch ICQ 11374583 markus@gaugusch.dhs.org
On Fri, 21 Jul 2000 rhoerbe@netpromote.co.at wrote:
- Setup ntp.conf. Try to find stratum 2 servers as close (ip-wise) as possible. hmmm ... i always used just netdate ts1.unvie.ac.at ts2.univie.ac.at (or any other timeservers) and run this from crontab every night ...
Don't think that this solution isn't good enough...
The nice thing about ntp is that it creates a drift file, so at boot time the system time is set properly (assuming the HW clock is off, which it almost always is). Also with ntp running you can synch other machines form it, 2 of my servers synch with other servers, then all my internal machines synch to my 2 local servers, and presto, everyone has the same (accurate) time. Checking logfiles/etc is a LOT easier. You'd be surprised how far a clock can drift in 24 hours, even if logs are onlyy off by like 5 seconds comparing them is a total pain.
greets Markus Gaugusch
-Kurt
participants (3)
-
Kurt Seifried -
Markus Gaugusch -
rhoerbe＠netpromote.co.at