From owner-freebsd-sparc64@FreeBSD.ORG Fri Aug 27 12:47:19 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 F1C6316A4CE; Fri, 27 Aug 2004 12:47:19 +0000 (GMT) Received: from the-macgregors.org (82-33-59-105.cable.ubr06.stav.blueyonder.co.uk [82.33.59.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id D94C343D45; Fri, 27 Aug 2004 12:47:18 +0000 (GMT) (envelope-from freebsd.macgregor@blueyonder.co.uk) X-Urban-Legend: Mail headers contain urban legends Received: from fire (rob@fire.macgregor [192.168.32.100]) (authenticated bits=0) by the-macgregors.org (8.13.1/8.13.1) with ESMTP id i7RClGku009570 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 27 Aug 2004 12:47:16 GMT Message-Id: <200408271247.i7RClGku009570@the-macgregors.org> From: "Rob MacGregor" To: "'Hiroki Sato'" , Date: Fri, 27 Aug 2004 13:47:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <20040827.211843.08645408.hrs@eos.ocn.ne.jp> Thread-Index: AcSMMElXBNfgA0EqTxi1vOlezK9FEQAA2DUw X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) Subject: RE: 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:47:20 -0000 On Friday, August 27, 2004 1:19 PM, Hiroki Sato <> unleashed the infinite monkeys and produced: > 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? AFAIK it's an NTP "issue" - your system is required to be within a number of years of "now" for it to be set. Trawl comp.protocols.time.ntp for details, or see the NTP documentation on the NTP website (www.ntp.org) where I remember this being discussed in the last few months (sorry I can't be more precise). -- Rob | Oh my God! They killed init! You bastards!