[70630] in North American Network Operators' Group
Re: ntp config tech note
daemon@ATHENA.MIT.EDU (Jared Mauch)
Thu May 20 17:33:54 2004
Date: Thu, 20 May 2004 17:33:22 -0400
From: Jared Mauch <jared@puck.nether.net>
To: Randy Bush <randy@psg.com>
Cc: nanog@nanog.org
In-Reply-To: <16557.8284.749771.291099@ran.psg.com>
Errors-To: owner-nanog-outgoing@merit.edu
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
--
Jared Mauch | pgp key available via finger from jared@puck.nether.net
clue++; | http://puck.nether.net/~jared/ My statements are only mine.
