From owner-freebsd-questions@freebsd.org Mon Aug 27 08:22:27 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50FB51090C55 for ; Mon, 27 Aug 2018 08:22:27 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id D5CD884024 for ; Mon, 27 Aug 2018 08:22:26 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 650A717A3D; Mon, 27 Aug 2018 17:22:17 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 09FA828874; Mon, 27 Aug 2018 17:22:17 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 1EC6D28873; Mon, 27 Aug 2018 17:22:15 +0900 (JST) Date: Mon, 27 Aug 2018 17:21:00 +0900 (JST) Message-Id: <20180827.172100.2296091074664550273.yasu@utahime.org> To: freebsd-questions@freebsd.org Subject: Re: named and ntpd start order in rc.d From: Yasuhiro KIMURA In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Aug 2018 08:22:27 -0000 From: Andrea Venturoli 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