1 |
On Jan 16, 2008 9:49 AM, Mark Knecht <markknecht@×××××.com> wrote: |
2 |
> |
3 |
> On Jan 16, 2008 5:09 AM, Mark Haney <mhaney@××××××××××××.org> wrote: |
4 |
> > Drake Donahue wrote: |
5 |
> > > |
6 |
> > > ----- Original Message ----- From: "Mark Haney" <mhaney@××××××××××××.org> |
7 |
> > > To: <gentoo-amd64@l.g.o> |
8 |
> > > Sent: Tuesday, January 15, 2008 10:22 AM |
9 |
> > > Subject: [gentoo-amd64] Problem with latest timezone update? |
10 |
> > > |
11 |
> > > |
12 |
> > >> Okay, here's something I can't seem to figure out. My laptop time |
13 |
> > >> doesn't want to stay sync'd. I always run ntpd at boot time to keep |
14 |
> > >> it in sync, but now, when I boot without an ethernet cable hooked up, |
15 |
> > >> it's over 5 hours off. It didn't do this until I updated the timezone |
16 |
> > >> just after Christmas. /etc/conf.d/clock is set to my timezone |
17 |
> > >> (EST5EDT) and /etc/localtime is symlinked to the correct timezone. |
18 |
> > >> |
19 |
> > >> I thought maybe the BIOS clock was wrong, but it's not 5 hours off, |
20 |
> > >> maybe a minute or so. I tried setting the HWclock to system time and |
21 |
> > >> that didn't fix it. Any ideas on what else to try? |
22 |
> > >> |
23 |
> > > Could it be this simple? Quoting: |
24 |
> > > |
25 |
> > > # /etc/conf.d/clock |
26 |
> > > |
27 |
> > > # Set CLOCK to "UTC" if your system clock is set to UTC (also known as |
28 |
> > > # Greenwich Mean Time). If your clock is set to the local time, then # |
29 |
> > > set CLOCK to "local". Note that if you dual boot with Windows, then # |
30 |
> > > you should set it to "local". |
31 |
> > > |
32 |
> > > CLOCK="local" |
33 |
> > > |
34 |
> > |
35 |
> > Yeah it could very well be. I didn't notice that before, but for some |
36 |
> > reason this file was changed. It's possible I did it and not realize |
37 |
> > it, but I was almost certain that I didn't update that file when I ran |
38 |
> > dispatch-conf. But then again, one of my other personalities might have |
39 |
> > done it. I'll have to ask around and see which one could have been the |
40 |
> > perp. Thanks for picking that up. |
41 |
> > |
42 |
> |
43 |
> I'm having problems after an emerge -DuN system this morning. What's |
44 |
> the proper solution to this? |
45 |
> |
46 |
> dragonfly ~ # date |
47 |
> Wed Jan 16 17:45:44 Local time zone must be set--see zic manual page 2008 |
48 |
> dragonfly ~ # |
49 |
> |
50 |
> My mythbackend server is Linux only. The clock line is currently set |
51 |
> to UTC. timezone is Los Angeles as it's always been. It's 9:45 as I |
52 |
> write this but the clock thinks it's 17:45. 8 hours ahead is GMT, |
53 |
> right? |
54 |
> |
55 |
> The hardware clock seems to be on GMT: |
56 |
> |
57 |
> dragonfly ~ # hwclock -r |
58 |
> Wed Jan 16 17:46:35 2008 -0.584758 seconds |
59 |
> dragonfly ~ # |
60 |
> |
61 |
> It seems the localtime file is messed up? |
62 |
> |
63 |
> dragonfly ~ # cat /usr/share/zoneinfo/localtime |
64 |
> TZif21Local time zone must be set--see zic manual pageTZif21Local time |
65 |
> zone must be set--see zic manual page |
66 |
> <Local time zone must be set--see zic manual page>0 |
67 |
> dragonfly ~ # |
68 |
> |
69 |
> Isn't that supposed to be a link to Los_Angeles in my case? Going to |
70 |
> check the latest install docs. |
71 |
> |
72 |
> - Mark |
73 |
> |
74 |
OK, the timezone update wiped out the /etc/localtime file. From the |
75 |
kernel config page: |
76 |
|
77 |
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=7 |
78 |
|
79 |
it tells me to copy Los_Angeles to /etc/localtime. After I did that I |
80 |
see this with date: |
81 |
|
82 |
dragonfly ~ # date |
83 |
Wed Jan 16 09:55:51 PST 2008 |
84 |
dragonfly ~ # |
85 |
|
86 |
- Mark |
87 |
-- |
88 |
gentoo-amd64@l.g.o mailing list |