1 |
On Saturday 11 February 2006 18:41, Mark Knecht wrote: |
2 |
> Hello, |
3 |
> Just in the last week or so my AMD64 machine has started to exhibit |
4 |
> problems with the clock. Maybe it's a hardware problem, or possibly |
5 |
> it's some new ntpd issue after updates. At boot time it seems to be |
6 |
> coming up with semi-random times. This is causing me to ask a few |
7 |
> questions and try to learn a bit more about how this actually works |
8 |
> under Linux. Thanks in advance. |
9 |
> |
10 |
> QUESTION 1: UTC vs. local |
11 |
> |
12 |
> In /etc/conf.d/clock I can choose UTC vs. local. Does this refer to |
13 |
> the time I set in the hardware clock or something else? Nominally it's |
14 |
> easier sitting here in California to set the hardware clock to |
15 |
> California time. Is there any problem with doing this? If I understand |
16 |
> the comments I should be using 'local' but the default seemed to be |
17 |
> UTC. |
18 |
|
19 |
it does not really matter which one you choose. |
20 |
|
21 |
> |
22 |
> QUESTION 2: date |
23 |
> |
24 |
> date only sets a software clock, correct? Is this all the system uses |
25 |
> after boot? |
26 |
|
27 |
man date says 'system time'. which is the 'software clock' |
28 |
|
29 |
> |
30 |
> QUESTION 3: hwclock -w |
31 |
> |
32 |
> This is supposed to write the time in the system's software clock into |
33 |
> hardware, correct? |
34 |
|
35 |
yes |
36 |
|
37 |
> |
38 |
> QUESTION 4: |
39 |
> |
40 |
> Does ntpd actually update the system clock, or is it another layer yet |
41 |
> on top. If I use ntpd and then do hwclock -w does an accurate time get |
42 |
> written to the hardware clock? |
43 |
# If you want to sync the system clock to the hardware clock during |
44 |
# shutdown, then say "yes" here. |
45 |
|
46 |
CLOCK_SYSTOHC="yes" |
47 |
|
48 |
btw, removing /etc/adjtime will help, if your clock behaves funny. |
49 |
yes |
50 |
|
51 |
you should open /etc/conf.d/clock and set this: |
52 |
-- |
53 |
gentoo-amd64@g.o mailing list |