From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 11:19:51 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 94CEB16A41F for ; Sun, 1 Jan 2006 11:19:51 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7F6643D45 for ; Sun, 1 Jan 2006 11:19:50 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail12.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k01BJlmn001319 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 1 Jan 2006 22:19:48 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k01BJkHh043925; Sun, 1 Jan 2006 22:19:46 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k01BJjGD043924; Sun, 1 Jan 2006 22:19:45 +1100 (EST) (envelope-from pjeremy) Date: Sun, 1 Jan 2006 22:19:45 +1100 From: Peter Jeremy To: Poul-Henning Kamp Message-ID: <20060101111945.GA42228@cirb503493.alcatel.com.au> References: <73774.1136109554@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <73774.1136109554@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: 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 11:19:51 -0000 On Sun, 2006-Jan-01 10:59:14 +0100, Poul-Henning Kamp wrote: >http://phk.freebsd.dk/misc/leapsecond.txt > >Notice how CLOCK_REALTIME recycles the 1136073599 second. Thank you (and others) for your efforts in getting FreeBSD to this point. I did find what appears to be two hosts that both held the leap indicator as "01", well after the leap second, until I unpeered them. My configuration is: firewall - 5.4-STABLE 3 internal hosts - 4.9, 6.0 and 7.0. All these systems peer each other. The firewall is additionally a client to a number of external servers (only 1 of which handled the leap second correctly). All my systems correctly handled the leap second. (Though I had to manually unconfig several external systems which failed to handle the leap second and threatened to compromise my clock by over-loading the false-ticker algorithm). My firewall reset the leap indicator bit at 0030 UTC and the 5.4 host reset it at about 0106 UTC. Neither the 6.0 nor 7.0 systems reset the leap bit until I unpeered them at 0500 UTC. I suspect that both systems saw the leap indicator bit in the NTP packets from each other and held each other's leap indicator set. Once I unpeered them, both reset their leap indicator bits. Happy New Year to all. -- Peter Jeremy