From owner-freebsd-stable@freebsd.org Sat Jul 11 02:30:35 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2D858F94 for ; Sat, 11 Jul 2015 02:30:35 +0000 (UTC) (envelope-from jamie@dyslexicfish.net) Received: from dyslexicfish.net (deadcat.mail.dyslexicfish.net [45.63.12.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BD271DE0 for ; Sat, 11 Jul 2015 02:30:34 +0000 (UTC) (envelope-from jamie@dyslexicfish.net) Received: from dyslexicfish.net (deadcat.mail.dyslexicfish.net [45.63.12.202]) by dyslexicfish.net (8.14.5/8.14.5) with ESMTP id t6B2U7us062286; Sat, 11 Jul 2015 03:30:07 +0100 (BST) (envelope-from jamie@dyslexicfish.net) Received: (from jamie@localhost) by dyslexicfish.net (8.14.5/8.14.5/Submit) id t6B2U61F062285; Sat, 11 Jul 2015 03:30:06 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201507110230.t6B2U61F062285@dyslexicfish.net> Date: Sat, 11 Jul 2015 03:30:06 +0100 To: john.marshall@riverwillow.com.au, freebsd-stable@freebsd.org Subject: Re: Will 10.2 also ship with a very stale NTP? References: <20150710235810.GA76134@rwpc16.gfn.riverwillow.net.au> In-Reply-To: <20150710235810.GA76134@rwpc16.gfn.riverwillow.net.au> User-Agent: Heirloom mailx 12.4 7/29/08 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-4.2.7 (dyslexicfish.net [45.63.12.202]); Sat, 11 Jul 2015 03:30:08 +0100 (BST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jul 2015 02:30:35 -0000 John Marshall wrote: > I also note that phk@ was working on an ntp client which he hoped to > offer as a replacement but that is presumably not ready yet. I also > note that we have current versions of ntp available in ports; but I'm > talking about what we ship in the base system. I realise you are talking about stable software in base, but for info, phk's replacement is called 'ntimed' and can be found on github, and also in /usr/ports/net/ntimed/ - it's unfinished and we are not advised to run it on production systems, but living dangerously, I've been running it on 4 servers for a few months with no issues (although I had to make some 'glue' changes to make it stable.) cheers, Jamie