| 1 |
Neil Bothwick wrote: |
| 2 |
> On Wed, 4 Feb 2009 13:38:11 +0000, Stroller wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>> So when I found the clock to be a week out of date I checked that ntpd |
| 6 |
>> appeared to be running (it was) and restarted it. The date remained |
| 7 |
>> the same. Stopping ntpd & starting ntp-client corrected the date |
| 8 |
>> immediately. |
| 9 |
>> |
| 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 |
|
| 17 |
To avoid running ntp-client and ntpd, look at the -g switch for ntpd. |
| 18 |
It will make the big jump once and then keep the clock in sync. |
| 19 |
|
| 20 |
Cheers, |
| 21 |
|
| 22 |
Drew |
| 23 |
|
| 24 |
-- |
| 25 |
Be a Great Magician! |
| 26 |
Visit The Alchemist's Warehouse |
| 27 |
|
| 28 |
http://www.alchemistswarehouse.com |
Archives