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
