Subject: Re: Clock
From: Charles Lepple (charles@ghz.cc)
Date: Thu Jun 07 2001 - 16:44:29 MDT
--On Thursday, June 07, 2001 3:42 PM -0500 Chris Ruprecht
<chrup999@yahoo.com> wrote:
> xntpd is way to complicated. You have to set up all these parameters - how
> many nanoseconds your machines takes to get the message from one to the
> other ...
Not really. The point behind xntpd is that a whole bunch of averaging and
filtering goes on behind the scenes so that you don't have to know the
delay characteristics of your WAN connection.
The only part that requires calibration (aside from external PPS sources)
is the authentication delay. You don't need that for a home machine.
I just have a few 'server ...' lines in my xntpd.conf file. The xntpd docs
have a nice list of servers throughout the 'net that you can use.
> I use rdate - just one command, executed once a day by 'cron' and
This can come back to haunt you, especially if the server you are
synchronizing to happens to restart with the wrong time. Unix in general
doesn't like it when the time jumps around, and xntpd will correct time
errors over longer periods of time.
The biggest culprit is X -- if you set your clock backwards or forwards
when X is running, events will get labeled with the wrong time, and it can
really confuse apps. Trust me on this one. Time-related errors with daemons
are even more difficult to diagnose.
-- Charles Lepple <charles@ghz.cc> http://ghz.cc/charles/
This archive was generated by hypermail 2a24 : Thu Jun 07 2001 - 15:50:21 MDT