Date: Fri, 27 Aug 2004 13:47:16 +0100 From: "Rob MacGregor" <freebsd.macgregor@blueyonder.co.uk> To: "'Hiroki Sato'" <hrs@freebsd.org>, <sparc64@freebsd.org> Subject: RE: 64bit time_t problem? Message-ID: <200408271247.i7RClGku009570@the-macgregors.org> In-Reply-To: <20040827.211843.08645408.hrs@eos.ocn.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408271247.i7RClGku009570>