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.50) id 1EfPzP-0002sT-Kd for garchives@archives.gentoo.org; Thu, 24 Nov 2005 22:54:52 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jAOMrZ3l016027; Thu, 24 Nov 2005 22:53:35 GMT Received: from psmtp02.wxs.nl (psmtp02.wxs.nl [195.121.247.11]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jAOMnMnp004703 for ; Thu, 24 Nov 2005 22:49:22 GMT Received: from graskamp (ip51cfa1ef.direct-adsl.nl [81.207.161.239]) by psmtp02.wxs.nl (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTP id <0IQH00MEBE26NZ@psmtp02.wxs.nl> for gentoo-user@lists.gentoo.org; Thu, 24 Nov 2005 23:49:18 +0100 (MET) Date: Thu, 24 Nov 2005 23:48:23 +0100 From: Benno Schulenberg Subject: Re: [gentoo-user] system clock keeps getting reset to weird times In-reply-to: <4384B0CC.5020403@wanadoo.fr> To: gentoo-user@lists.gentoo.org Message-id: <200511242348.23159.benno.schulenberg@gmail.com> 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 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.8.3 References: <200511181030.02690.ireneshusband@yahoo.co.uk> <200511212256.18057.benno.schulenberg@gmail.com> <4384B0CC.5020403@wanadoo.fr> X-Archives-Salt: 1ab054ec-4e79-48f5-87f8-fd75599c6dcb X-Archives-Hash: 33e5338c18a4ff4b6ae0643280670e02 Charles Trois wrote: > ~ # ls -l /etc/localtime > lrwxrwxrwx 1 root root 32 Nov 22 20:39 /etc/localtime -> > /usr/share/zoneinfo/Europe/Paris > > and in /etc/conf.d/clock: > > CLOCK="local" Did you maybe change this last one after your last reboot? Because then the system time won't have changed accordingly. Do a 'hwclock -hctosys' to set the system time from the hardware clock. > What else can I check? Is the clock initscript run? Check with 'rc-update -s'. If it is, try removing it from the startup sequence, see if that solves it. Is date maybe aliased? Check with 'type date'. Benno -- gentoo-user@gentoo.org mailing list