On Thu, 2004-07-29 at 17:34, Amnon wrote:
> We are doing it to two remote ones, but how does that help? The two we were
> getting it from were both at the same university though. Are you saying
> that if you get it from two different sources, it can make a decision which
> one is right???? :-)
You ideally want two or three different time sources in physically and
logically separate locations. This is so a fault at one site doesn't
corrupt all of your time sources (which sounds like what you were bitten
by).
The NTP daemon will use all of the time sources to arrive at a "correct"
time assuming that all of your sources are fairly close to "correct" as
well (e.g. fairly close to each other).
> Hey, not a bad idea at all !!! Why can't the client on the server see that
> the time is trying to change by more than a certain number of minutes/hours,
> and ignore the update?
It does. Most that I have seen will adjust up to a one hour difference,
but if it's greater than that will ask for manual correction.
General practice for a site is to designate your own internal time
source (typically a firewall but not necessarily), configure that system
to synchronize to two to five remote time sources, then configure all
other local systems to configure to that.
--
John Hardin KA7OHZ <[EMAIL PROTECTED]>
Internal Systems Administrator voice: (425) 672-1304
Apropos Retail Management Systems, Inc. fax: (425) 672-0192
-----------------------------------------------------------------------
If you smash a computer to bits with a mallet, that appears to count
as encryption in the state of Nevada.
- CRYPTO-GRAM 12/2001
-----------------------------------------------------------------------
