| 1 |
Stroller wrote: |
| 2 |
> Hi there, |
| 3 |
> |
| 4 |
> I just logged into one of my machines that has recently been powered |
| 5 |
> down for a few days - not a terribly common occurrence with my servers |
| 6 |
> - to find a date of January 30th showing. |
| 7 |
> |
| 8 |
> I used to run ntp-client, but AIUI adding this to the default runlevel |
| 9 |
> only sets the clock once at boot up. Of course the problem with that |
| 10 |
> is that the computer's clock can become inaccurate if the spring |
| 11 |
> tension is weak, as is obviously the case in my older PCs. |
| 12 |
> |
| 13 |
> So a while back I changed /etc/runlevels/default so that ntpd is |
| 14 |
> started instead. |
| 15 |
> |
| 16 |
> I understood that ntpd was not only a server for my LAN (a facility I |
| 17 |
> don't use) but that it would also periodically check the time with |
| 18 |
> upstream servers & keep the machine's clock in constant sync. |
| 19 |
> |
| 20 |
> So when I found the clock to be a week out of date I checked that ntpd |
| 21 |
> appeared to be running (it was) and restarted it. The date remained |
| 22 |
> the same. Stopping ntpd & starting ntp-client corrected the date |
| 23 |
> immediately. |
| 24 |
> |
| 25 |
> Before I do any investigation, can someone tell me if my understanding |
| 26 |
> so far is correct? Is ntpd supposed to keep the machine's clock in |
| 27 |
> constant sync, or is it only (say) a server to offer the date to |
| 28 |
> clients? (depending upon the clock being set correctly by other means) |
| 29 |
> I thought I had configured ntpd with upstream servers separately from |
| 30 |
> ntp-client. |
| 31 |
> |
| 32 |
> Stroller. |
| 33 |
> |
| 34 |
> |
| 35 |
|
| 36 |
I use ntpd here as well. Ntpd does not set it immediately like other |
| 37 |
commands do. From my understanding ntpd compares its time to a server |
| 38 |
then gradually adjusts the clock by speeding up or slowing down the |
| 39 |
clock. It takes a while to do this. If your clock is a long ways off |
| 40 |
then it will take longer. |
| 41 |
|
| 42 |
I'm not sure if this is still true but I read that if it is way off, |
| 43 |
several days or longer I would assume, it will require you to adjust it |
| 44 |
manually or you could set it with ntpdate which will set it instantly |
| 45 |
from one of the time servers. In this case, set the clock then restart |
| 46 |
ntpd. |
| 47 |
|
| 48 |
Hope that helps. |
| 49 |
|
| 50 |
Dale |
| 51 |
|
| 52 |
:-) :-) |
Archives