From owner-freebsd-stable@freebsd.org Fri Jul 24 09:35:28 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 8AF259A812E for ; Fri, 24 Jul 2015 09:35:28 +0000 (UTC) (envelope-from fbsd@xtaz.co.uk) Received: from mail.xtaz.uk (tao.xtaz.uk [IPv6:2001:8b0:202::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 55FB615EE for ; Fri, 24 Jul 2015 09:35:28 +0000 (UTC) (envelope-from fbsd@xtaz.co.uk) Received: by mail.xtaz.uk (Postfix, from userid 1001) id C304E20AEE9B; Fri, 24 Jul 2015 10:35:25 +0100 (BST) Date: Fri, 24 Jul 2015 10:35:25 +0100 From: Matt Smith To: freebsd-stable@freebsd.org Subject: Re: 10.2-BETA2 patch etc/ntp.conf to enable ntpd pool client functionality Message-ID: <20150724093525.GA1257@xtaz.uk> Mail-Followup-To: Matt Smith , freebsd-stable@freebsd.org References: <20150724022717.GA61649@rwpc16.gfn.riverwillow.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20150724022717.GA61649@rwpc16.gfn.riverwillow.net.au> User-Agent: Mutt/1.5.23 (2014-03-12) 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: Fri, 24 Jul 2015 09:35:28 -0000 On Jul 24 12:27, John Marshall wrote: >I have submitted a patch to the distributed ntp.conf to enable ntpd pool >client functionality. This was not possible in the ancient version of >ntpd shipped with FreeBSD releases over the past several years. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201803 > Thanks for this. But I would like to make some additional suggestions. There is no need to use multiple pools. You only need one. Pool works by using the minclock and maxclock values to work out how many peers it needs to add and keep track of. minclock is the minimum amount of * and + peers it should keep, and maxclock is the maximum amount of total peers including the actual pool itself. Also the local clock has been deprecated in favour of orphan mode. So I would suggest something like this instead: pool 0.freebsd.pool.ntp.org iburst tos minclock 3 maxclock 6 orphan 6 This will fire up a pool association and then add 5 peers from that pool and keep a minimum of 3 in * or + modes. If any become unreliable it will add more according to the min/maxclock values. For more info: http://support.ntp.org/bin/view/Support/OrphanMode http://lists.ntp.org/pipermail/questions/2010-April/026304.html -- Matt