svn commit: r326095 - head/usr.sbin/bsdinstall/scripts

[Ian Lepore]

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
> > > > <freebsd at pdx.rh.cn85.dnsmgr.net> 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