named and ntpd start order in rc.d

[Shane Ambler]

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