| 1 |
Mark Knecht wrote: |
| 2 |
> Hi Bob, |
| 3 |
> /etc/localtime seems to be OK: |
| 4 |
> |
| 5 |
> mark@lightning ~ $ ls -l /etc/localtime |
| 6 |
> lrwxrwxrwx 1 root root 39 Aug 30 10:29 /etc/localtime -> |
| 7 |
> /usr/share/zoneinfo/America/Los_Angeles |
| 8 |
> mark@lightning ~ $ |
| 9 |
> |
| 10 |
> My clock settings seem similar, other than the UTC/local question |
| 11 |
> |
| 12 |
> CLOCK="local" |
| 13 |
> CLOCK_OPTS="" |
| 14 |
> CLOCK_SYSTOHC="yes" |
| 15 |
> |
| 16 |
> Are you able to clarify about what to write into the clock when |
| 17 |
> using fist date and then hwclock? For instance yesterday I did these |
| 18 |
> commands: |
| 19 |
> |
| 20 |
> date 021008002006 |
| 21 |
> hwclock -w |
| 22 |
> |
| 23 |
> But this morning (Feb. 11th) when I booted the clock came up saying |
| 24 |
> Feb. 9th. so I had to write it again after booting. |
| 25 |
> |
| 26 |
> |
| 27 |
Are you using ntpd? If so, does ntp-client run correctly during boot? |
| 28 |
This is the preferred way to set the system clock. If ntpd is running, |
| 29 |
what does `ntpq -p' output? Does `rc-status default' indicate both |
| 30 |
ntp-client and ntpd as 'started'? |
| 31 |
|
| 32 |
> NOTE: The problem happens using both UTC and local so it's actually |
| 33 |
> not caused by that. |
| 34 |
> |
| 35 |
> NOTE 2: I also see that system time is off by 2 minutes from what I |
| 36 |
> get from the over the phone time system. Normally they have been very |
| 37 |
> close so it seems that ntpd is not doing it's job right now either.... |
| 38 |
> |
| 39 |
ntpd is definently not working then. ntpd gives up if the local clock |
| 40 |
is too far off of network time, that is where ntp-client becomes useful |
| 41 |
at bootup. |
| 42 |
|
| 43 |
|
| 44 |
BobS |
| 45 |
|
| 46 |
|
| 47 |
-- |
| 48 |
gentoo-amd64@g.o mailing list |
Archives