From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HlosH-0007gz-15 for garchives@archives.gentoo.org; Wed, 09 May 2007 16:18:45 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l49GHDPJ005326; Wed, 9 May 2007 16:17:13 GMT Received: from smtp26.msg.oleane.net (smtp26.msg.oleane.net [62.161.4.26]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l49GCp5L000370 for ; Wed, 9 May 2007 16:12:51 GMT Received: from smtp26.msg.oleane.net (localhost [127.0.0.1]) by smtp26.msg.oleane.net (MTA-AV) with ESMTP id l49GCorl008760 for ; Wed, 9 May 2007 18:12:50 +0200 Received: from [192.168.1.157] ([81.80.76.230]) (authenticated) by smtp26.msg.oleane.net (MTA) with ESMTP id l49GCoQ4008738 for ; Wed, 9 May 2007 18:12:50 +0200 Message-ID: <4641F2FE.709@magellium.fr> Date: Wed, 09 May 2007 18:12:46 +0200 From: Redouane Boumghar Organization: Magellium User-Agent: Thunderbird 1.5.0.10 (X11/20070316) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Clock is way off References: <49bf44f10705081656s776f28f5kbe497a5326107c2f@mail.gmail.com> <49bf44f10705090727q3d727147pdeacfb9a502cf002@mail.gmail.com> <20070509155458.62ec598f@hactar.digimed.co.uk> In-Reply-To: <20070509155458.62ec598f@hactar.digimed.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PFSI-Info: PMX 5.3.1.294258 (no virus found) X-Archives-Salt: 5533ad38-1359-47ea-8df9-ccdfd031ef35 X-Archives-Hash: 5dadbaf437e6451c21090e29659e7140 Hello everyone, I recently had to reset my clock to a more "correct" (that may be subjective) setting. In your case I would set my /etc/conf.d/clock file as: CLOCK="UTC" TIMEZONE="US/Pacific" then I would assure that my /etc/localtime file is correct with the next command: $ cp /usr/share/zoneinfo/US/Pacific /etc/localtime If you have no zoneinfo files then consider emerging 'timezone-data'. The setting like that should be fine and if you have an offset it's that your hardware clock must be set to a time that is considered as UTC (since you have "CLOCK=UTC" in your conf) while it's not. So set your clock correctly with rdate, ntp whatever... and then write your system clock to your hardware clock (I guess this action is done at shut down). You may use the following command : $ hwclock --systohc Then your machine is ready to have correct time as UTC. Be sure to have your profile environnement variable TZ to be set to your timezone. In your .profile : export TZ="US/Pacific"; Concerning dual boot.. as I am in !! Everywhere I could see advice to set my CLOCK var to "local" but that's always a mess with the timezone... so the simple thing is to deactivate the Microsoft Windows update or at least to set it to UTC time.. Thus keeping CLOCK="UTC" which would be a quite good standard. But I understand Gentoo is installed to cause no harm to Windows, thats why there is this CLOCK="local" attitude I guess. Hope that helps I'd be happy to share the pros and the cons... -- Redouane BOUMGHAR Physics, Remote Sensing and Digital Imagery Engineer Neil Bothwick wrote: > On Wed, 9 May 2007 14:27:52 +0000, Grant wrote: > >> I have: >> >> -rw-r--r-- 1 root root 255 Apr 25 20:58 /etc/localtime >> >> on the laptop with the incorrect time, and the router with the correct >> time. > > That only tells us that /etc/localtime is a file, not which timezone data > it contains. Re-emerging timezone-data will ensure that it has the data > for the timezone you specified in /etc/conf.d/clock. > > Setting the timezone in /etc/conf.d/clock has no effect until you next > emerge timezone-data. A 255 byte /etc/localtime is probably either Factory > or localtime, i.e. nothing has been set. > > -- gentoo-user@gentoo.org mailing list