From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 21:24:28 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B3AA16A420; Sun, 1 Jan 2006 21:24:28 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91E9E43D7C; Sun, 1 Jan 2006 21:24:26 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k01LNYoe097389; Sun, 1 Jan 2006 14:23:35 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 01 Jan 2006 14:23:37 -0700 (MST) Message-Id: <20060101.142337.33509370.imp@bsdimp.com> To: dfr@nlsystems.com From: "M. Warner Losh" In-Reply-To: <200601011643.35578.dfr@nlsystems.com> References: <73774.1136109554@critter.freebsd.dk> <200601011643.35578.dfr@nlsystems.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 01 Jan 2006 14:23:35 -0700 (MST) Cc: phk@phk.freebsd.dk, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 21:24:28 -0000 In message: <200601011643.35578.dfr@nlsystems.com> Doug Rabson writes: : On Sunday 01 January 2006 09:59, Poul-Henning Kamp wrote: : > http://phk.freebsd.dk/misc/leapsecond.txt : > : > Notice how CLOCK_REALTIME recycles the 1136073599 second. : > : > Happy new-year! : : Mmmmm... Leap seconds... I can hear Warner grinding his teeth from : here :-) Having experienced on has not changed my deep, and abiding feelings for leapseconds in the least. I've spent about 120 hours on leap seconds in the past couple of years. For something so damn simple, these are a huge pita. Most of the time has been determining what real devices will do over a leap second, which information is reliable and which information lags and how. There's too damn many variables to know what information you can rely on and what information you have to 'filter' and how. You can make the data streams more reliable at the cost of code complexity and inflexibility. I guess that's a long way of saying that I hate Leap Seconds. They are too damn complicated for such a simple concept :-( Wanrer