On Wed, 17 Oct 2001 19:03:30 EDT, Tom Allison writes: >Additional comment. >ntpd on Server 'A' will not accept any time synchronization requests until it >is satisfied it's got a reasonable time, then Computer 'B' will be able to >synchronize with Server 'A'. >After you run ntpdate and start ntpd -- wait a little while. If you need to >know exactly how long - watch tcpdump for the ntp traffic to die down a >little bit and then try it. >I find 10 minutes is a very good number.
Unfortunately, if you've got a whole bunch of servers waiting to start to synchronize with your main time server(s). In a hierarchical environment you can get up to hours until they all are in sync :( Running ntpdate and starting ntpd immediately after doesn`t address that problem, I'm afraid. But that, I guess, is the tradeoff for ntpds deep black, but very precise magic... cheers, &rw -- -- Documentation is like sex: when it is good, it is very, very good; -- and when it is bad, it is better than nothing. - Dick Brandon
pgpL20EMuMROR.pgp
Description: PGP signature
