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 1JFX57-0003Mh-09 for garchives@archives.gentoo.org; Thu, 17 Jan 2008 15:55:05 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 728D0E0884; Thu, 17 Jan 2008 15:55:03 +0000 (UTC) Received: from QMTA04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [76.96.30.40]) by pigeon.gentoo.org (Postfix) with ESMTP id 1B018E0884 for ; Thu, 17 Jan 2008 15:55:03 +0000 (UTC) Received: from OMTA14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by QMTA04.emeryville.ca.mail.comcast.net with comcast id eDe61Y0051HpZEs0A0D600; Thu, 17 Jan 2008 15:55:02 +0000 Received: from iwillxp333 ([68.58.192.35]) by OMTA14.emeryville.ca.mail.comcast.net with comcast id eFuK1Y00C0mGrD88a00000; Thu, 17 Jan 2008 15:54:20 +0000 X-Authority-Analysis: v=1.0 c=1 a=URvBFtrbUXwA:10 a=TWrJej8CVZXJRHtCA6gA:9 a=XCQHf_QLe3jnM2eV0F0A:7 a=ogTTMZBDlHmzDXBnRsveGwfbS_cA:4 a=MSl-tDqOz04A:10 a=si9q_4b84H0A:10 a=plE8mkVoi54A:10 Message-ID: <001501c85921$21dbb9a0$0200a8c0@iwillxp333> From: "Drake Donahue" To: References: <478CCFC3.8080503@ercbroadband.org> <001701c85798$40c49650$0200a8c0@iwillxp333> <478E0212.8040503@ercbroadband.org> <5bdc1c8b0801160949v77b0bef4yc6ff899c0e7d26cd@mail.gmail.com> <5bdc1c8b0801160957s48a2f651ha452ba2fc04e68aa@mail.gmail.com> <1200524500.25783.0.camel@kilik.ubersekret.info> <000601c858a3$d1dcef50$0200a8c0@iwillxp333> <5bdc1c8b0801161737v5d1e71dfi89a3bf4f75e77e0f@mail.gmail.com> <20080117101512.GA28923@litchinko.fr> <5bdc1c8b0801170708p6524b12aw5ad04ced9af43cc1@mail.gmail.com> Subject: Re: [gentoo-amd64] Problem with latest timezone update? Date: Thu, 17 Jan 2008 10:53:38 -0500 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: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archives-Salt: 36fae0ba-26fb-4d8e-9742-e06c0d36d766 X-Archives-Hash: 1812e05167fa2a0785b8c51cbb14ae82 ----- Original Message ----- From: "Mark Knecht" To: Sent: Thursday, January 17, 2008 10:08 AM Subject: Re: [gentoo-amd64] Problem with latest timezone update? > On Jan 17, 2008 2:15 AM, Nicolas Litchinko wrote: >> Hi, >> >> On Wed, Jan 16, 2008 at 05:37:21PM -0800, Mark Knecht wrote: >> > On Jan 16, 2008 4:56 PM, Drake Donahue wrote: >> > > Thus etc-update and/or dispatch-conf can't change localtime; but can >> > > change >> > > whether localtime runs or not. >> > >> > Humm...seems like what you say is true but doesn't explain how emerge >> > -DuN system changed the file. It was clearly changed since I could >> > look inside with vi and compare to the Los_Angeles file and see that >> > they were clearly different... >> >> There's a variable in /etc/conf.d/clock that controls whether or not >> /etc/localtime should be updated when a new version of >> sys-libs/timezone-data is merged: TIMEZONE. If this variable is set, the >> specified timezone data file is copied over /etc/localtime. >> >> as you can read in /etc/conf.d/clock: >> # Select the proper timezone. For valid values, peek inside of the >> # /usr/share/zoneinfo/ directory. For example, some common values are >> # "America/New_York" or "EST5EDT" or "Europe/Berlin". If you want to >> # manage /etc/localtime yourself, set this to "". >> >> If TIMEZONE is not set, /etc/localtime is not updated by >> sys-libs/timezone-data. However, if TIMEZONE is set to an invalid value, >> then /etc/localtime is overwritten by the "Factory" timezone data file. >> >> etc-update has probably changed the value of this variable after a >> baselayout update. Then a timezone-data update used the wrong value to >> update /etc/localtime. In your, case, the value of TIMEZONE should be >> TIMEZONE="America/Los_Angeles". >> >> -- >> Nicolas Litchinko >> BOFH excuse #348: >> We're on Token Ring, and it looks like the token got loose. >> -- >> gentoo-amd64@lists.gentoo.org mailing list >> >> > > OK, I buy it. My setup was missing the underscore: > > dragonfly ~ # cat /etc/conf.d/clock | grep TIMEZONE > TIMEZONE="America/LosAngeles" > dragonfly ~ # > > However time on the machine has been fine for the 2 years we've had > the machine. Has this been wrong the whole time and I jsut got lucky > or did someone possibly change the formatting? Postulated sequence: 2 years ago, most probably, TIMEZONE="PST8PDT" was used. All went well until a recent oops with etc-update or dispatch-conf, an inadvertent CLOCK="UTC", which caused the clock to start keeping universal time. A similar problem discussed here reported a solution which included using TIMEZONE="America/New_York" (I think, maybe America/Los_Angeles, maybe ...). Having the same universal time problem, you adopted the geographic idea but were then bitten by a typo. Of note, the old TIMEZONE="EST5EDT" continues to work fine here. > > Thanks for the clarification! > > Cheers, > Mark > -- > gentoo-amd64@lists.gentoo.org mailing list > -- gentoo-amd64@lists.gentoo.org mailing list