Date: Tue, 14 Jul 2015 15:33:05 +0100 From: krad <kraduk@gmail.com> To: Paul Mather <paul@gromit.dlib.vt.edu> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Circular dependency between local_unbound and ntpd? Message-ID: <CALfReye4Byhv0dX%2B2JVm=CEuAPnDitYOwgBFm_071Qwg_jvP_g@mail.gmail.com> In-Reply-To: <EDD17B95-0EA7-4C97-836D-7707416C0F07@gromit.dlib.vt.edu> References: <EDD17B95-0EA7-4C97-836D-7707416C0F07@gromit.dlib.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
As $ grep REQUIRE /etc/rc.d/ntpd # REQUIRE: DAEMON ntpdate FILESYSTEMS devfs You could set something similar to the following in the rc.conf ntpdate_hosts="a.b.c.d w.x.y.z" ntpdate_enable=yes On 14 July 2015 at 14:43, Paul Mather <paul@gromit.dlib.vt.edu> wrote: > I believe I ran afoul of a circular dependency between local_unbound and > ntpd on my 10.2-PRERELEASE system. I use a stock /etc/ntp.conf and use > ntpd_sync_on_start="YES". > > Last night, a BIOS settings reset cause my CMOS clock to go WAY out of > synch for the first time. No problem, I thought: NTP will correct it at > boot. > > Wrong! > > When my system booted, the time was not corrected. Also, DNS resolution > was not working. I figured out it was because local_unbound relies on an > accurately set clock, but the clock could not be set accurately because my > stock ntp.conf requires working DNS resolution to reach the NTP servers. > > That sounds like a potential circular dependency to me. > > My workaround at the time was to look up 0.freebsd.pool.ntp.org on > another system; stop ntpd; then do a ntpdate using the IP addresses to set > the clock. Once the clock was set accurately, things were all hunky dory. > > Does anyone have any suggestion for an automatic way around this? I guess > one way would be to put the IP address of an NTP server into my ntp.conf > file, so at least one would be reachable without needing a working DNS? > > My main concern is for those systems like my Raspberry Pi and Beaglebone > Black that don't have a battery-backed clock. I currently don't use > local_unbound on those, but it seems like I'd encounter this problem > routinely if I did. > > Cheers, > > Paul. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALfReye4Byhv0dX%2B2JVm=CEuAPnDitYOwgBFm_071Qwg_jvP_g>