From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JFE0r-0008Gh-EY for garchives@archives.gentoo.org; Wed, 16 Jan 2008 19:33:25 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5FEE5E0972; Wed, 16 Jan 2008 19:33:24 +0000 (UTC) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by pigeon.gentoo.org (Postfix) with ESMTP id DCE95E0972 for ; Wed, 16 Jan 2008 19:33:23 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id e21so382756fga.14 for ; Wed, 16 Jan 2008 11:33:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=BhaHD0xOmtYqHuXfv0b+y8BS1Fm7fcFCUbS2heMpGaE=; b=C5SOsm0VVUTaTESyEaLp+ngnlmDXNwl0AYTigG1mL2LEY6qbYPoaH8GQuWq9AEExIWD9QulhZBg1n4Yx9oLEhEdT3/f0fa4365X8+PdDp+iJ78rNj/CoTUeHlDbJv5Gc1BcbrsURuNA5SZLGw+b19nAnMGO629Achk585G0Jlw8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=NHYrYkSS+iLWttIelrd1jlcUCmKVcL+4z8EHnprDutv46+HMoR6/WXUZ10rRpC69grjmwgh8M/psrF9vxX4yJpyyw0erkgWysLMirsijw+1QdOlT+XYA5opy+qDLaSYrAZTtIompeO4PegqQ/8a2QlFangSKEAZmoEwFfbWMk7M= Received: by 10.82.174.20 with SMTP id w20mr2077199bue.28.1200512002655; Wed, 16 Jan 2008 11:33:22 -0800 (PST) Received: by 10.82.141.15 with HTTP; Wed, 16 Jan 2008 11:33:22 -0800 (PST) Message-ID: Date: Wed, 16 Jan 2008 19:33:22 +0000 From: Beso To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Problem with latest timezone update? In-Reply-To: <5bdc1c8b0801160957s48a2f651ha452ba2fc04e68aa@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_23829_7493902.1200512002647" References: <478CCFC3.8080503@ercbroadband.org> <001701c85798$40c49650$0200a8c0@iwillxp333> <478E0212.8040503@ercbroadband.org> <5bdc1c8b0801160949v77b0bef4yc6ff899c0e7d26cd@mail.gmail.com> <5bdc1c8b0801160957s48a2f651ha452ba2fc04e68aa@mail.gmail.com> X-Archives-Salt: d78143c8-a456-43fb-8293-0b276256a70b X-Archives-Hash: d2a20c24044fcb828fee56e87c0c714b ------=_Part_23829_7493902.1200512002647 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline that's one reason to use dispatch-conf over etc-update... at least you have the diff on the files that are to be modified and you can chose what to do file per file... 2008/1/16, Mark Knecht : > > On Jan 16, 2008 9:49 AM, Mark Knecht wrote: > > > > On Jan 16, 2008 5:09 AM, Mark Haney wrote: > > > Drake Donahue wrote: > > > > > > > > ----- Original Message ----- From: "Mark Haney" < > mhaney@ercbroadband.org> > > > > To: > > > > 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 > > 0 > > dragonfly ~ # > > > > Isn't that supposed to be a link to Los_Angeles in my case? Going to > > check the latest install docs. > > > > - Mark > > > OK, the timezone update wiped out the /etc/localtime file. From the > kernel config page: > > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=7 > > it tells me to copy Los_Angeles to /etc/localtime. After I did that I > see this with date: > > dragonfly ~ # date > Wed Jan 16 09:55:51 PST 2008 > dragonfly ~ # > > - Mark > -- > gentoo-amd64@lists.gentoo.org mailing list > > -- dott. ing. beso ------=_Part_23829_7493902.1200512002647 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline that's one reason to use dispatch-conf over etc-update... at least you have the diff on the files that are to be modified and you can chose what to do file per file...

2008/1/16, Mark Knecht < markknecht@gmail.com>:
On Jan 16, 2008 9:49 AM, Mark Knecht < markknecht@gmail.com> wrote:
>
> On Jan 16, 2008 5:09 AM, Mark Haney <mhaney@ercbroadband.org> wrote:
> > Drake Donahue wrote:
> > >
> > > ----- Original Message ----- From: "Mark Haney" <mhaney@ercbroadband.org>
> > > To: < gentoo-amd64@lists.gentoo.org>
> > > 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
>
OK, the timezone update wiped out the /etc/localtime file. From the
kernel config page:

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=7

it tells me to copy Los_Angeles to /etc/localtime. After I did that I
see this with date:

dragonfly ~ # date
Wed Jan 16 09:55:51 PST 2008
dragonfly ~ #

- Mark
--
gentoo-amd64@lists.gentoo.org mailing list




--
dott. ing. beso ------=_Part_23829_7493902.1200512002647-- -- gentoo-amd64@lists.gentoo.org mailing list