[70728] in North American Network Operators' Group
Re: ntp config tech note
daemon@ATHENA.MIT.EDU (Tony Li)
Sun May 23 19:05:22 2004
In-Reply-To: <Pine.LNX.4.44.0405232134140.17939-100000@server2.tcw.telecomplete.net>
Cc: Jared Mauch <jared@puck.nether.net>, Randy Bush <randy@psg.com>,
<nanog@nanog.org>
From: Tony Li <tony.li@tony.li>
Date: Sun, 23 May 2004 16:04:35 -0700
To: "Stephen J. Wilcox" <steve@telecomplete.co.uk>
Errors-To: owner-nanog-outgoing@merit.edu
It needs to be set of trusted time sources that is as reliable as you
feel is necessary.
If you're feeling extremely paranoid, then you can use the -g flag to
peer with a number
of your private stratum 1 sources and then let the sanity checking do
its job to
avoid any bogochimers.
Tony
On May 23, 2004, at 1:37 PM, Stephen J. Wilcox wrote:
>
> 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
>>
>>
>
