On 8/23/05, Bruno Lustosa <[EMAIL PROTECTED]> wrote: > On 8/23/05, kashani <[EMAIL PROTECTED]> wrote: > > That offset looks rather large. NTP really wants to make constant small > > changes, not a single huge change. This is why the ntpd setup allows for > > an immediate sync via ntpdate before starting the daemon. To fix this > > I'd shut down ntpd, run ntpdate 192.168.7.1, and then start ntpd again. > > That's what I did yesterday before leaving work. It synced with > ntpdate, and I left ntpd running. Today, the offset was like that. > That's what I don't understand. Hmmmm... If you specify one timeserver, ntp cannot tell which clock is drifting away (local or remote). Ntpd trusts the local clock more than the remote one. Large offsets cause ntpd to discard 192.168.7.1 as reliable timesource. Try adding on this one machine more time servers and observe what will happen.
-- Regards Karol Krzak -- gentoo-user@gentoo.org mailing list
