From owner-svn-src-head@freebsd.org Fri Nov 24 19:41:45 2017 Return-Path: Delivered-To: svn-src-head@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 3817EDEFB06 for ; Fri, 24 Nov 2017 19:41:45 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C70692A90 for ; Fri, 24 Nov 2017 19:41:44 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 52d26ccd-d14f-11e7-b805-f37e907b5733 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 52d26ccd-d14f-11e7-b805-f37e907b5733; Fri, 24 Nov 2017 19:40:29 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id vAOJePOa001595; Fri, 24 Nov 2017 12:40:25 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1511552425.52392.1.camel@freebsd.org> Subject: Re: svn commit: r326095 - head/usr.sbin/bsdinstall/scripts From: Ian Lepore To: Emmanuel Vadot , Allan Jude Cc: rgrimes@freebsd.org, cem@freebsd.org, src-committers , svn-src-all@freebsd.org, svn-src-head@freebsd.org, owner-src-committers@freebsd.org Date: Fri, 24 Nov 2017 12:40:25 -0700 In-Reply-To: References: <201711231729.vANHTVmo092083@pdx.rh.CN85.dnsmgr.net> <38787424-ff48-df5e-0831-922d14f1603c@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2017 19:41:45 -0000 On Fri, 2017-11-24 at 20:23 +0100, Emmanuel Vadot wrote: > On 2017-11-24 17:46, Allan Jude wrote: > > > > On 11/23/2017 12:29, Rodney W. Grimes wrote: > > > > > > [ 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 ... > > > > > 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. > > > > > > > > > > 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 > > > > Does ntpdate work out of the box in such environments?  If so, how? > > > ntpdate time.nist.gov > > > > > > ntpdate does not need a configureration file, just a command > > > line argument. > > > > > > > > The point of this thread was which option the installer should use to > > implement 'set the correct time on first boot'. >   The main point yes. >   I guess that I'll revert my commit and open a review which removes  > ntpd_sync_on_start and always add -g to rc_flags and people could  > argument there. I think this idea is a non-starter.  Avoiding time-steps is an important requirement in some sites.  As another message in this thread pointed out, restarting ntpd on a running system could result in a step if -g is a default. -- Ian