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.54) id 1F2sTo-0001pg-Rp for garchives@archives.gentoo.org; Sat, 28 Jan 2006 15:59:13 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k0SFwjN7030586; Sat, 28 Jan 2006 15:58:45 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k0SFwitd000369 for ; Sat, 28 Jan 2006 15:58:44 GMT Received: from mics.radio-msu.net ([158.250.0.18] helo=gw.mics.msu.su) by smtp.gentoo.org with esmtp (Exim 4.54) id 1F2sTL-0002xA-Do for gentoo-user-ru@lists.gentoo.org; Sat, 28 Jan 2006 15:58:43 +0000 Received: from localhost (mics.radio-msu.net [158.250.0.18]) by gw.mics.msu.su (8.13.4/8.13.4) with ESMTP id k0SFwxI1031688 for ; Sat, 28 Jan 2006 18:59:01 +0300 (MSK) (envelope-from pva@gentoo.org) Subject: Re: Re[2]: [gentoo-user-ru] clock From: "Peter Volkov (pva)" To: gentoo-user-ru@lists.gentoo.org In-Reply-To: <5010371024.20060128022833@sandy.ru> References: <315ad3a40601250846v7b9d2dc2w@mail.gmail.com> <43D8D8FC.3060301@gmail.ru> <43D9E7FB.6020204@vstu.ac.ru> <200601291609.35444.zeromancer@yandex.ru> <5010371024.20060128022833@sandy.ru> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-vJ4TlKUE3VI53hbRhvxR" Date: Sat, 28 Jan 2006 18:59:42 +0300 Message-Id: <1138463983.19832.24.camel@localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user-ru@gentoo.org Reply-To: gentoo-user-ru@gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 X-Virus-Scanned: by amavisd-new X-Archives-Salt: 6d4cf1e3-a034-4faa-8d0f-cb0fab713ad8 X-Archives-Hash: e63d0fa57e2d35d566af11e04df19419 --=-vJ4TlKUE3VI53hbRhvxR Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On =D0=A1=D0=B1=D1=82, 2006-01-28 at 02:28 +0300, Kanogin A.A. wrote: > =D0=9D=D0=B0 i815 - =D0=B2=D0=BE=D0=BE=D0=B1=D1=89=D0=B5 =D0=BD=D0=B0 =D1= =87=D0=B0=D1=81 =D0=B2=D0=BF=D0=B5=D1=80=D0=B5=D0=B4 =D0=BF=D1=80=D1=8B=D0= =B3=D0=B0=D1=8E=D1=82 =D0=BF=D0=BE=D1=81=D0=BB=D0=B5 =D0=BF=D0=B5=D1=80=D0= =B5=D0=B7=D0=B0=D0=B3=D1=80=D1=83=D0=B7=D0=BA=D0=B8 :) > =D0=93=D0=B4=D0=B5 =D0=BF=D0=BE=D1=87=D0=B8=D1=82=D0=B0=D1=82=D1=8C =D0= =BF=D1=80=D0=BE =D0=B4=D0=B0=D0=BD=D0=BD=D1=83=D1=8E =D1=84=D0=B8=D1=87=D1= =83? =D0=AF =D0=B4=D1=83=D0=BC=D0=B0=D1=8E =D0=B2=D0=B0=D0=BC =D0=BD=D0=B0=D0=B4= =D0=BE =D1=83=D0=B4=D0=B0=D0=BB=D0=B8=D1=82=D1=8C /etc/adjtime. =D0=98 =D0=B2=D0=BE=D1=82 =D0=BF=D0=BE=D1=81=D1=82 =D0=B8=D0=B7 gentoo-user= . =D0=94=D1=83=D0=BC=D0=B0=D1=8E =D0=BE=D0=BD =D0=BF=D0=BE=D0=BC=D0=BE=D0= =B6=D0=B5=D1=82 =D1=87=D0=B0=D1=81=D1=82=D0=B8=D1=87=D0=BD=D0=BE =D1=80=D0= =B0=D0=B7=D0=BE=D0=B1=D1=80=D0=B0=D1=82=D1=8C=D1=81=D1=8F. From:=20 Benno Schulenberg Reply-To:=20 gentoo-user@lists.gentoo.org To:=20 gentoo-user@lists.gentoo.org Subject:=20 Re: [gentoo-user] Wrong time on reboot. Not a CMOS battery problem. Date:=20 Fri, 27 Jan 2006 22:25:33 +0100 (=D0=A1=D0=B1=D1=82, 00:25 MSK) Abhay Kedia wrote: > Then, I shutdown the system and boot after a few hours. What I > see is that Gentoo sets the system time to the same one at which > I halted it. For example if I shutdown 4 hours ago at 14:00 hrs > and boot at 18:00 hrs, it will still set the time to 14:00 hrs > instead of the correct time. Try running 'hwclock --show --debug', and run it again a bunch of=20 seconds later. Is the hardware clock ticking? Here's a sample output: # hwclock --show --debug hwclock from util-linux-2.12r hwclock: Open of /dev/rtc failed, errno=3D2: No such file or=20 directory. Using direct I/O instructions to ISA clock. Last drift adjustment done at 1138395601 seconds after 1969 Last calibration done at 1138395601 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2006/01/27 21:04:32 Hw clock time : 2006/01/27 21:04:32 =3D 1138395872 seconds since 1969 Fri Jan 27 22:04:32 2006 -0.579761 seconds If it is ticking , then set the hardware clock to the correct time=20 with 'hwclock --set --date=3D', then throw away the=20 /etc/adjtime file. Throw it away, as it might be the adjusting=20 feature that thinks your clock is drifting a full hour per hour=20 (that is: ticks away two hours in one). > # /etc/conf.d/clock > CLOCK=3D"local" Do you need the "local" time thing? If Linux is the only OS on your=20 box it's easier to use UTC. Your time zone is set correctly? Where is /etc/localtime linking=20 to? Benno --=-vJ4TlKUE3VI53hbRhvxR Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD25Tuz6tlgEWSarMRAjuwAKCjudT0PGsgLhL0vkQuuI5wGySJagCfXlGv FVGzOFT/TDphce3OsIHxQxg= =dFJA -----END PGP SIGNATURE----- --=-vJ4TlKUE3VI53hbRhvxR-- -- gentoo-user-ru@gentoo.org mailing list