Re: [gentoo-amd64] Problem with latest timezone update?

[Mark Knecht]

On Jan 16, 2008 5:09 AM, Mark Haney <mhaney@××××××××××××.org> wrote:
> Drake Donahue wrote:
> >
> > ----- Original Message ----- From: "Mark Haney" <mhaney@××××××××××××.org>
> > To: <gentoo-amd64@l.g.o>
> > Sent: Tuesday, January 15, 2008 10:22 AM
> > Subject: [gentoo-amd64] Problem with latest timezone update?
> >
> >
> >> Okay, here's something I can't seem to figure out.  My laptop time
> >> doesn't want to stay sync'd.  I always run ntpd at boot time to keep
> >> it in sync, but now, when I boot without an ethernet cable hooked up,
> >> it's over 5 hours off.  It didn't do this until I updated the timezone
> >> just after Christmas.  /etc/conf.d/clock is set to my timezone
> >> (EST5EDT) and /etc/localtime is symlinked to the correct timezone.
> >>
> >> I thought maybe the BIOS clock was wrong, but it's not 5 hours off,
> >> maybe a minute or so.  I tried setting the HWclock to system time and
> >> that didn't fix it.  Any ideas on what else to try?
> >>
> > Could it be this simple? Quoting:
> >
> > # /etc/conf.d/clock
> >
> > # Set CLOCK to "UTC" if your system clock is set to UTC (also known as
> > # Greenwich Mean Time).  If your clock is set to the local time, then #
> > set CLOCK to "local".  Note that if you dual boot with Windows, then #
> > you should set it to "local".
> >
> > CLOCK="local"
> >
>
> Yeah it could very well be. I didn't notice that before, but for some
> reason this file was changed.  It's possible I did it and not realize
> it, but I was almost certain that I didn't update that file when I ran
> dispatch-conf.  But then again, one of my other personalities might have
> done it.  I'll have to ask around and see which one could have been the
> perp.  Thanks for picking that up.
>

I'm having problems after an emerge -DuN system this morning. What's
the proper solution to this?

dragonfly ~ # date
Wed Jan 16 17:45:44 Local time zone must be set--see zic manual page 2008
dragonfly ~ #

My mythbackend server is Linux only. The clock line is currently set
to UTC. timezone is Los Angeles as it's always been. It's 9:45 as I
write this but the clock thinks it's 17:45. 8 hours ahead is GMT,
right?

The hardware clock seems to be on GMT:

dragonfly ~ # hwclock -r
Wed Jan 16 17:46:35 2008  -0.584758 seconds
dragonfly ~ #

It seems the localtime file is messed up?

dragonfly ~ # cat /usr/share/zoneinfo/localtime
TZif21Local time zone must be set--see zic manual pageTZif21Local time
zone must be set--see zic manual page
<Local time zone must be set--see zic manual page>0
dragonfly ~ #

Isn't that supposed to be a link to Los_Angeles in my case? Going to
check the latest install docs.

- Mark
-- 
gentoo-amd64@l.g.o mailing list