From owner-freebsd-sparc64@FreeBSD.ORG Fri Aug 27 12:20:03 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FD0216A4CF for ; Fri, 27 Aug 2004 12:20:03 +0000 (GMT) Received: from smtp.eos.ocn.ne.jp (eos.ocn.ne.jp [222.146.51.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D61543D1F for ; Fri, 27 Aug 2004 12:20:03 +0000 (GMT) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p25049-adsao12honb4-acca.tokyo.ocn.ne.jp [219.161.86.49]) by smtp.eos.ocn.ne.jp (Postfix) with ESMTP id C3F4225BF for ; Fri, 27 Aug 2004 21:20:01 +0900 (JST) Received: from localhost (alph.allbsd.org [192.168.0.10]) by delta.allbsd.org (8.12.9p2/8.12.9) with ESMTP id i7RCJUA2081763 for ; Fri, 27 Aug 2004 21:19:30 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Fri, 27 Aug 2004 21:18:43 +0900 (JST) Message-Id: <20040827.211843.08645408.hrs@eos.ocn.ne.jp> To: sparc64@FreeBSD.org From: Hiroki Sato X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 4.0.66 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Fri_Aug_27_21_18_43_2004_765)--" Content-Transfer-Encoding: 7bit Subject: 64bit time_t problem? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Aug 2004 12:20:03 -0000 ----Security_Multipart(Fri_Aug_27_21_18_43_2004_765)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I noticed that after the system clock set too far in the future, ntpdate could not reset it properly. I tried the following (on 5.3-BETA1): # date 207008270000 ; ntpdate 192.168.100.1 ; date Wed Aug 27 00:00:00 JST 2070 Looking for host 192.168.100.1 and service ntp host found : xxx.allbsd.org 27 Aug 21:00:13 ntpdate[552]: step time server 192.168.100.1 offset -;0446744071497267106.746178 sec Fri Aug 27 21:00:13 JST 2004 # date 210008270000 ; ntpdate 192.168.100.1 ; date Fri Aug 27 00:00:00 JST 2100 Looking for host 192.168.100.1 and service ntp host found : xxx.allbsd.org 4 Oct 03:26:57 ntpdate[521]: step time server 192.168.100.1 offset 1265599617.382757 sec Tue Oct 4 03:26:57 JST 2140 # date 227008270000 ; ntpdate 192.168.100.1 ; date Password: Sat Aug 27 00:00:00 JST 2270 Looking for host 192.168.100.1 and service ntp host found : xxx.allbsd.org 10 Nov 09:57:37 ntpdate[564]: step time server 192.168.100.1 offset 195904656.965267 sec Fri Nov 10 09:57:37 JST 2276 The time set by ntpdate has a period of about 136 years depending on the previous time. I think this is problematic because the system clock can go wrong when the box is left in a power-off state, for example. Probably the time is handled in 32-bit somewhere, but I am not sure where it is. Is this a known problem or is there some workaround? -- | Hiroki SATO ----Security_Multipart(Fri_Aug_27_21_18_43_2004_765)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBLyajTyzT2CeTzy0RAtZ0AJ9y1T3B3pDq3U9QVlCX9TtuXnoskACgjagr moNuiBmMFgF8slTASTqaIaQ= =XNeS -----END PGP SIGNATURE----- ----Security_Multipart(Fri_Aug_27_21_18_43_2004_765)----