Date: Wed, 29 Aug 2018 03:40:31 +0930 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: Andrea Venturoli <ml@netfence.it>, freebsd-questions@freebsd.org Subject: Re: named and ntpd start order in rc.d Message-ID: <26752c19-2a58-965b-bdfb-06dd84b732e4@ShaneWare.Biz> In-Reply-To: <2a9b79b1-2b57-98d3-9b4e-53eb4a9768b8@netfence.it> References: <e651e86a-76d4-391c-9d38-9be8448bb455@netfence.it> <20180827.172100.2296091074664550273.yasu@utahime.org> <2a9b79b1-2b57-98d3-9b4e-53eb4a9768b8@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29/8/18 12:06 am, Andrea Venturoli wrote: > On 8/27/18 10:21 AM, Yasuhiro KIMURA wrote: > >> What are the versions of FreeBSD and BIND(named) you use? > > # freebsd-version > 11.2-RELEASE-p2 > # pkg info | grep bind > bind911-9.11.4P1 BIND DNS suite with updated DNSSEC and > > > >> "rcorder /etc/rc.d* /usr/local/etc/rc.d*" gets following result. > > In fact, > >> # rcorder /etc/rc.d/* /usr/local/etc/rc.d/* | grep -E "(ntp|named)" >> /usr/local/etc/rc.d/named >> /etc/rc.d/ntpdate >> /etc/rc.d/ntpd > So named starts before ntpd. While I see ntpd failing during boot, I never looked into whether it was working during uptime. Actually I get named in between ntpdate and ntpd, but I also get unknown provision and circular dependency errors from rcorder. % freebsd-version 11.2-STABLE % pkg info -x bind bind913-9.13.2 % rcorder /etc/rc.d/* /usr/local/etc/rc.d/* | grep -E "(ntp|named)" /etc/rc.d/ntpdate /usr/local/etc/rc.d/named /etc/rc.d/ntpd On 27/8/18 2:04 am, Andrea Venturoli wrote: > > That bug (of the 7.0 era) was closed as fixed, since /etc/rc.d/ntpd > requires ntpdate, which in turn required named. -- FreeBSD - the place to B...Software Developing Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26752c19-2a58-965b-bdfb-06dd84b732e4>