On Tue, Oct 17, 2006 at 12:12:23PM -0400, Roberto C. Sanchez wrote: > On Mon, Oct 16, 2006 at 05:23:15PM -0700, Andrew Sackville-West wrote: > > On Mon, Oct 16, 2006 at 08:02:12PM -0300, Henrique de Moraes Holschuh wrote: > > > > > > Any NTP drift above half a second means something is completely broken, so > > > *none* of your client machines are working fine. The two servers seem to > > > work right. Make sure to also configure the two servers to *peer* each > > > other, btw. > > > > vague memories in my head that ntp won't sync more than a half second > > or so at a time, you have to use something else to get them closer and > > then ntp can do it. I've used ntpdate in the past as a one-time sync > > and then its worked after that. Also had a machine that was drifter > > faster than ntp could keep up with, but after a few days of hitting > > ntpdate randomly, it was able to calculate the drift enough to keep up > > after that point. this is all vague memory, ymmv widely. > > > > A > > Hmm. I've used date (not ntpdate) to get the clock back to within a > couple of seconds of my local NTP server. But it always drifts away > again. Perhaps I should try ntpdate? I just used ntpdate so that I could automatically get a good time and not worry about it. You're also getting better help than I good ever offer on the other part of this thread. good luck A
Attachment:
signature.asc
Description: Digital signature