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 1JFRmF-0007ti-5d for garchives@archives.gentoo.org; Thu, 17 Jan 2008 10:15:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4B5ADE07B1; Thu, 17 Jan 2008 10:15:13 +0000 (UTC) Received: from insomnia.sylvain-lebon.fr (ns1.sylvain-lebon.fr [88.191.42.101]) by pigeon.gentoo.org (Postfix) with ESMTP id 20B49E07B1 for ; Thu, 17 Jan 2008 10:15:13 +0000 (UTC) Received: by insomnia.sylvain-lebon.fr (Postfix, from userid 1002) id 43858140EC; Thu, 17 Jan 2008 11:15:12 +0100 (CET) Date: Thu, 17 Jan 2008 11:15:12 +0100 To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Problem with latest timezone update? Message-ID: <20080117101512.GA28923@litchinko.fr> Mail-Followup-To: gentoo-amd64@lists.gentoo.org 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> 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; charset=us-ascii Content-Disposition: inline In-Reply-To: <5bdc1c8b0801161737v5d1e71dfi89a3bf4f75e77e0f@mail.gmail.com> User-Agent: Mutt/1.5.11 From: nicolas@litchinko.fr (Nicolas Litchinko) X-Archives-Salt: ac536341-70c7-4830-8743-177dd754659c X-Archives-Hash: b7f89aefd5c676c871cf7aa3b8fd75a1 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