On Wed, Feb 04, 2009 at 06:20:50PM +0000, Stroller wrote: > > On 4 Feb 2009, at 14:11, Neil Bothwick wrote: >> On Wed, 4 Feb 2009 13:38:11 +0000, Stroller wrote: >> >>> So when I found the clock to be a week out of date I checked that ntpd >>> appeared to be running (it was) and restarted it. The date remained >>> the same. Stopping ntpd & starting ntp-client corrected the date >>> immediately. >> >> ntpd will not change the time if the difference is too large, the man >> page gives the limit. You need to run both at boot; ntp-client sets the >> time immediately, no matter what the skew, then ntpd keeps the clock in >> time. > > I see. Many thanks. > > I am surprised my clock got so far out of whack, having been only switched > off a few days. I don't think the battery is completely dead. The > difference in behaviour seems unexpected, but surely makes sense from the > developers' point-of-view. > > I will set both in the default runlevel & keep an eye on things. > > Stroller.
Another method would be using the chrony program (a simpler alternative to ntp). I've been using it for the last 5+ years, and consider it a simple and usable program. Ciao, Wolfgang
