Date: Mon, 27 Aug 2018 17:21:00 +0900 (JST) From: Yasuhiro KIMURA <yasu@utahime.org> To: freebsd-questions@freebsd.org Subject: Re: named and ntpd start order in rc.d Message-ID: <20180827.172100.2296091074664550273.yasu@utahime.org> In-Reply-To: <e651e86a-76d4-391c-9d38-9be8448bb455@netfence.it> References: <e651e86a-76d4-391c-9d38-9be8448bb455@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Andrea Venturoli <ml@netfence.it> Subject: named and ntpd start order in rc.d Date: Sun, 26 Aug 2018 18:34:43 +0200 > I'm in the same situation described in this bug: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=129146 > > ntpd starts when named is not yet running, fails to resolve its peers > and never works again until I restart it manually. > > That bug (of the 7.0 era) was closed as fixed, since /etc/rc.d/ntpd > requires ntpdate, which in turn required named. > However, the latest statement is not true anymore, today (probably due > to the fact that named is no longer in base). > > I guess I'm not the only one who has this problem and I wonder how > others are solving this issue. > Also, should I add a comment to that bug or open a new one? What are the versions of FreeBSD and BIND(named) you use? I use bind912-9.12.2P1_1(dns/bind912) on 11.2-RELEASE, and "rcorder /etc/rc.d* /usr/local/etc/rc.d*" gets following result. yasu@maybe[2006]% rcorder /etc/rc.d/* /usr/local/etc/rc.d/* (snip) /etc/rc.d/syslogd /usr/local/etc/rc.d/tcsd /usr/local/etc/rc.d/named /etc/rc.d/watchdogd /etc/rc.d/savecore /etc/rc.d/archdep /etc/rc.d/abi /etc/rc.d/SERVERS /usr/local/etc/rc.d/tpmd /etc/rc.d/accounting /etc/rc.d/ntpdate /etc/rc.d/rpcbind (snip) /etc/rc.d/local /etc/rc.d/lpd /etc/rc.d/motd /etc/rc.d/mountlate /etc/rc.d/nscd /etc/rc.d/ntpd /etc/rc.d/powerd (snip) So named, ntpdate and ntpd is started expected order in my environment. --- Yasuhiro KIMURA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180827.172100.2296091074664550273.yasu>