From owner-freebsd-sparc64@FreeBSD.ORG Sat Aug 28 22:48:25 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 EE3F616A4CF; Sat, 28 Aug 2004 22:48:25 +0000 (GMT) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id A12C643D1D; Sat, 28 Aug 2004 22:48:25 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from [10.0.1.3] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.11/8.12.3) with ESMTP id i7SMmM2q032515; Sat, 28 Aug 2004 18:48:23 -0400 (EDT) (envelope-from brad@stop.mail-abuse.org) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: <20040829.054111.102114690.hrs@eos.ocn.ne.jp> References: <20040827.211843.08645408.hrs@eos.ocn.ne.jp> <200408271247.i7RClGku009570@the-macgregors.org> <20040829.054111.102114690.hrs@eos.ocn.ne.jp> Date: Sun, 29 Aug 2004 00:35:55 +0200 To: Hiroki Sato From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: sparc64@freebsd.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: Sat, 28 Aug 2004 22:48:26 -0000 At 5:41 AM +0900 2004-08-29, Hiroki Sato wrote: > m> AFAIK it's an NTP "issue" - your system is required to be within a > m> number of years of "now" for it to be set. Trawl > m> comp.protocols.time.ntp for details, or see the NTP documentation > m> on the NTP website (www.ntp.org) where I remember this being > m> discussed in the last few months (sorry I can't be more precise). > > Thanks for the pointer. I will look into them. You definitely don't want to try to use NTP to set the time if the offset is too large. Modern versions of ntpd can make a one-time stepping change if you add the "-g" option on the command line, but even that can only take you so far. While FreeBSD on sparc64 might now have a 64-bit time_t, but I don't know that the protocol can handle this large of a difference. Try setting the date manually to something reasonably close (i.e., less than 136 years), then using ntpd to get the "real" time. -- Brad Knowles, "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See for more info.