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