From owner-svn-src-all@freebsd.org Thu Nov 23 21:33:54 2017 Return-Path: Delivered-To: svn-src-all@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 D34F8DF630C; Thu, 23 Nov 2017 21:33:54 +0000 (UTC) (envelope-from devin@shxd.cx) Received: from shxd.cx (mail.shxd.cx [64.201.244.140]) (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 C4D187B96B; Thu, 23 Nov 2017 21:33:54 +0000 (UTC) (envelope-from devin@shxd.cx) Received: from [64.201.244.132] (port=63059 helo=[10.0.0.101]) by shxd.cx with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1eHwNV-000Bb9-Gc; Thu, 23 Nov 2017 18:37:37 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: svn commit: r326095 - head/usr.sbin/bsdinstall/scripts From: Devin Teske X-Mailer: iPhone Mail (13G36) In-Reply-To: <201711231729.vANHTVmo092083@pdx.rh.CN85.dnsmgr.net> Date: Thu, 23 Nov 2017 13:33:50 -0800 Cc: cem@freebsd.org, Emmanuel Vadot , src-committers , svn-src-all@freebsd.org, svn-src-head@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <201711231729.vANHTVmo092083@pdx.rh.CN85.dnsmgr.net> To: rgrimes@freebsd.org X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Nov 2017 21:33:54 -0000 > On Nov 23, 2017, at 9:29 AM, Rodney W. Grimes wrote: >=20 > [ Charset UTF-8 unsupported, converting... ] >> On Thu, Nov 23, 2017 at 7:17 AM, Rodney W. Grimes >> wrote: >>>> Also we do provide an ntp.conf so ... >>>=20 >>> We do, a template, all commented out, and does not work for >>> machines behind strong firewalls that wont allow ntp out >>> to the net but have internal ntp servers that are used for >>> such things. >>>=20 >>> Well maybe not all commented out, I think it defaults to >>> some public pools. I believe it would be missing iburst >>> for use with ntp -pg >>=20 >> Does ntpdate work out of the box in such environments? If so, how? >=20 > ntpdate time.nist.gov >=20 > ntpdate does not need a configureration file, just a command > line argument. >=20 >=20 At the banks we used to rely on both (in this order) ntpdate running and the= n ntpd running. Running ntpdate before ntpd meant that on a [re]boot, ntpdate would jump the= box to the appropriate time, regardless of how far behind the clock was (th= ink "dead cmos battery" on a system left powered-off for a long time). Meanwhile, running ntpd *without* the sync-on-start feature meant we could b= ounce the ntpd service as necessary and it would always adhere to the limit w= e set on it -- one hour to prevent syncing on systems which had been manuall= y adjusted by greater than an hour for some one-off instances. --=20 Devin