From owner-freebsd-questions@FreeBSD.ORG Sat Dec 6 00:10:34 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FFFC106567B for ; Sat, 6 Dec 2008 00:10:34 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id A866F8FC1E for ; Sat, 6 Dec 2008 00:10:33 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from phenom.cordula.ws (phenom [192.168.254.60]) by fw.farid-hajji.net (Postfix) with ESMTP id 8A2C73644F; Sat, 6 Dec 2008 01:10:31 +0100 (CET) Message-ID: <4939C33A.8070108@cordula.ws> Date: Sat, 06 Dec 2008 01:11:38 +0100 From: cpghost User-Agent: Thunderbird 2.0.0.18 (X11/20081126) MIME-Version: 1.0 To: RW References: <560f92640811211647q551daccnaec4e8085bb8e042@mail.gmail.com> <20081205190703.0dfb952d@gumby.homeunix.com> In-Reply-To: <20081205190703.0dfb952d@gumby.homeunix.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: named and ntpd start order in rc.d X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2008 00:10:34 -0000 RW wrote: > On Fri, 21 Nov 2008 16:47:50 -0800 > "Nerius Landys" wrote: > > >> I believe that the fix for this is to add a dependency >> to /etc/rc.d/ntpd script, adding "named" to "REQUIRE" section in >> comments. In your opinion, is this a robust fix? For example the >> line in my /etc/rc.d/ntpd script that looks like so: >> >> # REQUIRE: DAEMON ntpdate cleanvar devfs >> >> would be changed to this: >> >> # REQUIRE: DAEMON ntpdate cleanvar devfs named >> > > This shouldn't be needed as ntpd already requires ntpdate and in > turn ntpdate requires named. The issue is probably timing - that named > isn't ready. > > I have a similar issue with PPP not having connected by the time > ntpdate runs , so I just have a script that runs between named and > ntpdate, and blocks waiting for access. > Those timing / start-order issues are getting more and more annoying, IMHO. On my PPPoE / mpd5 connected systems, it's the same problem: * openntpd (from ports) can't start, because named is not ready * pf can't parse /etc/pf.conf because the ng0 interface is not yet there etc, etc, etc... Isn't there a generic way to delay some scripts from starting until a specific subset is ready (say: networking fully up, and named ready to reply)? Perhaps some keyword or class to add to a startup script would be nice to have! Thanks, --cpghost. -- Cordula's Web. http://www.cordula.ws/