From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-1.2 required=5.0 tests=DKIM_ADSP_NXDOMAIN, DMARC_MISSING,MAILING_LIST_MULTI,NICE_REPLY_A autolearn=unavailable autolearn_force=no version=4.0.0 Received: from mailnews.kub.nl (mailnews.kub.nl [137.56.0.220]) by chiba.3jane.net (Postfix) with ESMTP id 81C14AC492 for ; Thu, 18 Jul 2002 05:07:55 -0500 (CDT) Received: from mail.sub.devrieze.net (gt0416.kub.nl [137.56.97.162]) by mailnews.kub.nl (8.12.2/8.12.2) with ESMTP id g6IA7ivA022864 for ; Thu, 18 Jul 2002 12:07:49 +0200 (MET DST) Received: from pavlvs1.local.devrieze.net (pavlvs1.local.devrieze.net [192.168.1.1]) by mail.sub.devrieze.net (Postfix) with ESMTP id 981793CC0 for ; Thu, 18 Jul 2002 12:07:43 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" From: Paul de Vrieze To: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] Weird system time issue Date: Thu, 18 Jul 2002 12:07:41 +0200 User-Agent: KMail/1.4.2 References: <001901c22d2b$8bc98a40$6501a8c0@neptune> <200207171110.38413.pauldv@cs.kun.nl> <200207171811.13916.michael@kyrana.com> In-Reply-To: <200207171811.13916.michael@kyrana.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200207181207.41713.pauldv@cs.kun.nl> Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 034bd6e3-a749-459c-b8e8-a420aefaa6e4 X-Archives-Hash: 3ac01a858b5ef27242c85da4ba023f03 On Thursday 18 July 2002 00:11, Michael Mattsson wrote: > On July 17, 2002 05:10 am, Paul de Vrieze wrote: > > Did you also try to remove /etc/adjtime. This file gets written by th= e > > hwclock utility and is supposed to help in autoadjusting your hardwar= e > > clock to the real time (clocks are never entirely correct). Also (as = I > > posted earlier) using rdate (or ntpdate for that matter) not at boot > > breaks things. Specially with cron as it's whole time system gets > > confused. > > No. But I did notice that when i set the system to use "localtime" ins= tead > of "UTC", the problem does not appear. > That looks like an adjtime problem (which timezone are you, the further f= rom=20 gmt the bigger the problems). Basically what you want to do is first deci= de=20 whether you store your time in UTC or in localtime (the latter if you run= =20 windows, else the first). Then set the computer time correct (ntpdate for= =20 example). Then set the hardware clock correct (yes you have two clocks) u= sing=20 "hwclock --utc --systohc" for utc and "hwclock --localtime --systohc" for= =20 localtime. Next delete the /etc/adjtime file so the system will start to = zero=20 with correcting your computer time to systematic drift (that is not reall= y=20 nescesarry if you have ntpd anyway) Paul --=20 Paul de Vrieze Junior Researcher Mail: pauldv@cs.kun.nl Homepage: http://www.devrieze.net