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 1JFWMb-0000rj-C3 for garchives@archives.gentoo.org; Thu, 17 Jan 2008 15:09:05 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 91405E05AC; Thu, 17 Jan 2008 15:08:53 +0000 (UTC) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237]) by pigeon.gentoo.org (Postfix) with ESMTP id 6F21BE05AC for ; Thu, 17 Jan 2008 15:08:53 +0000 (UTC) Received: by wr-out-0506.google.com with SMTP id c49so208339wra.1 for ; Thu, 17 Jan 2008 07:08:53 -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:content-transfer-encoding:content-disposition:references; bh=QgpTOX4bNcQ5EwTdU9hSQfssag7TS8s1ENevX/g1+WA=; b=kcP0hk7H1+YJLTcjMfmT8SHxanx9rJoPutTITQc7x6UvJUxXxwky0ELH285vpoGsQnuWD1V3b3jHcFUKFwEX/WuF/pMKXpmNfukGxx98recmQwZy4eWoUu+yCWyacaHqR5E8F3jkSfy/3EqqzFKJjXXIpSvYSsqMSpPzydfmtXk= 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:content-transfer-encoding:content-disposition:references; b=TY60dHG+rufAoN7GX0JmPV3WUwqj1NeNEkU0WMIRz4kAaffjpIPwp9d+eLmQshxMwSC64sgaZDQ2I60f4+IAVlhGM+mMp6HAYGhV9pE1M60axHcpx4LKuS09EYaTPXeAl/AzcExqGCkSYvDnAmnFCFOuokPGxqzoVBIdDSY3FRk= Received: by 10.142.101.17 with SMTP id y17mr1277546wfb.54.1200582532405; Thu, 17 Jan 2008 07:08:52 -0800 (PST) Received: by 10.142.12.9 with HTTP; Thu, 17 Jan 2008 07:08:52 -0800 (PST) Message-ID: <5bdc1c8b0801170708p6524b12aw5ad04ced9af43cc1@mail.gmail.com> Date: Thu, 17 Jan 2008 07:08:52 -0800 From: "Mark Knecht" To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Problem with latest timezone update? In-Reply-To: <20080117101512.GA28923@litchinko.fr> 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=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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> X-Archives-Salt: 9b3f6542-dde2-4752-8ec6-3d8080d16bc6 X-Archives-Hash: f30e46f2b8d1c9fecd27a004dd8f2cae 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? Thanks for the clarification! Cheers, Mark -- gentoo-amd64@lists.gentoo.org mailing list