Date: Tue, 10 Jan 2017 16:11:14 -0500 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Ian Lepore <ian@freebsd.org> Cc: jungle Boogie <jungleboogie0@gmail.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: NTP boot at start on bbone black Message-ID: <D611B144-13F5-43E4-9877-E40E9F44C04C@gromit.dlib.vt.edu> In-Reply-To: <1484080340.96230.90.camel@freebsd.org> References: <CAKE2PDvxy4H6Qi_sTh1kUB1OVQ2TiAJoYOwe9w=Vb8U2aon6GQ@mail.gmail.com> <1484080340.96230.90.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 10, 2017, at 3:32 PM, Ian Lepore <ian@freebsd.org> wrote: > On Tue, 2017-01-10 at 12:26 -0800, jungle Boogie wrote: >> Sorry, forgot a subject! >>=20 >> On 10 January 2017 at 12:26, jungle Boogie <jungleboogie0@gmail.com> >> wrote: >>>=20 >>> Hi All, >>>=20 >>> Running latest 12-current snapshot on a beagle bone black: >>> % uname -a >>> FreeBSD beaglebone 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r311461: >>> Fri >>> Jan 6 03:13:01 UTC 2017 >>> root@releng3.nyi.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/BEAGLEB >>> ONE >>> arm >>>=20 >>> I have ntp setup to start at boot: >>> % cat /etc/rc.conf >>> hostname=3D"beaglebone" >>> ifconfig_DEFAULT=3D"DHCP" >>> sshd_enable=3D"YES" >>> sendmail_enable=3D"NONE" >>> sendmail_submit_enable=3D"NO" >>> sendmail_outbound_enable=3D"NO" >>> sendmail_msp_queue_enable=3D"NO" >>> growfs_enable=3D"YES" >>> ntpd_enable=3D"YES" >>>=20 >>> And yet, no ntp process is running. >>>=20 >>> % ntpq -p >>> ntpq: read: Connection refused >>>=20 >>>=20 >>> What's the trick to get ntp to start at boot to sync time? >>>=20 >>> Thanks! >=20 >=20 > Add ntpd_sync_on_start=3DYES and it should work. Ntpd is most likely > panicking and exiting because it's afraid to step the clock more than > 1000 seconds, which is needed on systems that don't have a battery- > backed clock and start up with a time far in the past. Using the sync > on start option gives ntpd permission to step the clock any amount it > needs to, just one time at startup. As an alternative, I'm using the net/ntimed package on my BeagleBone = Black and other FreeBSD/arm systems. It's lightweight, reliable, and = easy to use if all you want to do is keep your clock synchronised with = other NTP hosts on the network. Cheers, Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D611B144-13F5-43E4-9877-E40E9F44C04C>