[70722] in North American Network Operators' Group
Re: ntp config tech note
daemon@ATHENA.MIT.EDU (Stephen J. Wilcox)
Sun May 23 16:38:03 2004
Date: Sun, 23 May 2004 21:37:18 +0100 (BST)
From: "Stephen J. Wilcox" <steve@telecomplete.co.uk>
To: Jared Mauch <jared@puck.nether.net>
Cc: Randy Bush <randy@psg.com>, <nanog@nanog.org>
In-Reply-To: <20040520213322.GA32355@puck.nether.net>
Errors-To: owner-nanog-outgoing@merit.edu
I would be very worried about forcing an unchecked clock sync against a single
time source in this way.. if your source is broken you can break a lot..
i think the limit is 1000s so you shouldnt be slipping by that much unless
something is broken?
Steve
On Thu, 20 May 2004, Jared Mauch wrote:
> I've found it useful on older machines (PCs with cheap clocks and
> oscilators) to cron ntpdate once an hour to prevent the clock from
> getting too far off by itself. I've found the daemon doesn't do good enough
> of a job to sync on it's own...
>
> I'm also wondering, how many people are using the ntp.mcast.net
> messages to sync their clocks? what about providing ntp
> to your customers via the "ntp broadcast" command on
> serial links, etc..?
>
> - jared
>
>
