Date: Thu, 23 Nov 2017 01:33:39 -0800 From: Devin Teske <devin@shxd.cx> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: Ian Lepore <ian@freebsd.org>, Emmanuel Vadot <manu@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org, owner-src-committers@freebsd.org Subject: Re: svn commit: r326095 - head/usr.sbin/bsdinstall/scripts Message-ID: <821D3401-1DA8-46B5-BF5C-AAC3BDA3D8F3@shxd.cx> In-Reply-To: <df40d9f9214ec5fea0790fc3a94add44@megadrive.org> References: <201711221527.vAMFRlTc041361@repo.freebsd.org> <1511368688.46031.1.camel@freebsd.org> <df40d9f9214ec5fea0790fc3a94add44@megadrive.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 22, 2017, at 11:15 PM, Emmanuel Vadot <manu@bidouilliste.com> wrote= : >=20 >> On 2017-11-22 17:38, Ian Lepore wrote: >>> On Wed, 2017-11-22 at 15:27 +0000, Emmanuel Vadot wrote: >>> Author: manu >>> Date: Wed Nov 22 15:27:47 2017 >>> New Revision: 326095 >>> URL: https://svnweb.freebsd.org/changeset/base/326095 >>> Log: >>> bsdinstall: Add ntpdate option >>> =20 >>> When you install a computer for the first time, the date in the CMOS s= ometimes >>> not accurate and you need to ntpdate as ntpd will fail a the time diff= erence >>> is too big. >>> Add an option in bsdinstall to enable ntpdate that will do that for us= . >>> =20 >>> Reviewed by: allanjude >>> Differential Revision: https://reviews.freebsd.org/D13149 >>> Modified: >>> head/usr.sbin/bsdinstall/scripts/services >>> Modified: head/usr.sbin/bsdinstall/scripts/services >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D >>> --- head/usr.sbin/bsdinstall/scripts/services Wed Nov 22 15:18:11 201= 7 (r326094) >>> +++ head/usr.sbin/bsdinstall/scripts/services Wed Nov 22 15:27:47 201= 7 (r326095) >>> @@ -46,6 +46,8 @@ DAEMONS=3D$( dialog --backtitle "FreeBSD Installer" \ >>> local_unbound "Local caching validating resolver" ${local_unbound:-= off} \ >>> sshd "Secure shell daemon" ${sshd_enable:-off} \ >>> moused "PS/2 mouse pointer on console" ${moused_enable:-off} \ >>> + ntpdate "Synchronize system and network time at bootime" \ >>> + ${ntpdate_enable:-off} \ >>> ntpd "Synchronize system and network time" ${ntpd_enable:-off} \= >>> powerd "Adjust CPU frequency dynamically if supported" \ >>> ${powerd_enable:-off} \ >> The right way to enable a time-step at boot is to set the rc conf >> variable ntpd_sync_on_start to YES. ntpdate has been deprecated for >> *years*. >> -- Ian >=20 > Hi Ian, >=20 > Thanks I didn't know about option -g (nor ntpd_sync_on_start), this bring a= few questions : >=20 > - Is there any reason to not always use -g for ntpd ? As a lambda user I j= ust want my time to be set, no matter what. > - Should we remove ntpdate in -current before 12 if it's deprecated ? >=20 > I'll make the necessary changes according to your (or others) answers. >=20 I would not remove ntpdate. Is there a way to make ntpd sync and then quit immediately? If not, sounds like ntpdate serves a purpose not filled by ntpd. Valid case is someone running a VM that gets paused for days, weeks, or even= months at a time. On such a VM it may make more sense to let the clock be o= nly sporadically managed in an adhoc manner. I personally like to use ntpdate on said VMs because I generally set a timeo= ut on my ssh-agent in said VMs and by managing the clock manually allows me t= o better control keys loaded. Pretty sure other people may have other reasons for non-daemonized clock man= agement. --=20 Devin=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?821D3401-1DA8-46B5-BF5C-AAC3BDA3D8F3>