From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 12:46:12 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D3BB1065680 for ; Thu, 15 Jan 2009 12:46:12 +0000 (UTC) (envelope-from mkhitrov@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 0522D8FC1C for ; Thu, 15 Jan 2009 12:46:11 +0000 (UTC) (envelope-from mkhitrov@gmail.com) Received: by bwz13 with SMTP id 13so3655579bwz.19 for ; Thu, 15 Jan 2009 04:46:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=A8EtmSgoaZmUx6Wb4kcxGN6PM4CJ6hoLJaddsV3M04c=; b=DHGCI9dDZ85g50QkX6U1O7np5/1IG+OKI4xmPuVBiCAzVMYHjXR41OfbTmKZPN2ZvT geWfbH7oRie2ADQLH/OUTuz5IC9uMWTEkcC5t2YagRydl8EzbRJmbGKuh5ygH5UNRth2 u8hg8jzs2ofz6gdy2K9482IngW9NMuoxKDeyE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KQxbeSg49hgl7uHaKTm5EuS77zTC07J1Vu+iZAoOQwLFx2VsivNoSU60SD07HLKc9i vgNXdVE4UQJGBXYgE5GpGQ1HqALrIVOJMUmnUFTuL/jMFEvLye/SMKwd6Hlz/eXyTRKx WeMPtA10cabx8S+GIwqVw7cOuak8joFUblAHc= MIME-Version: 1.0 Received: by 10.223.110.144 with SMTP id n16mr1512625fap.63.1232022159627; Thu, 15 Jan 2009 04:22:39 -0800 (PST) In-Reply-To: <20090115051422.GA59032@duncan.reilly.home> References: <20090115051422.GA59032@duncan.reilly.home> Date: Thu, 15 Jan 2009 07:22:39 -0500 Message-ID: <26ddd1750901150422t11ca7188hf4f3f25b797f8a61@mail.gmail.com> From: Maxim Khitrov To: Andrew Reilly Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: roam@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to get djbdns to start early enough to satisfy ntpd at boot? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 12:46:13 -0000 On Thu, Jan 15, 2009 at 12:14 AM, Andrew Reilly wrote: > Hi there, > > I've been a happy djbdns+tinydns user for many, many years. I > want to keep using it, so answers of the form "bletch! Use ISC > BIND the way BSD intended" will be ignored :-) > > Having said that, one annoying consequence of my transition > some time ago to using ntpd, rather than just setting the clock > once-off with ntpdate as I used to, is that the /etc/rc.d > mechanism starts ntpd before /usr/local/etc/rc.d/svscan.sh > starts svscan, which starts /services/dnscache. That wouldn't > matter if ntpd was a bit sensible and just kept trying to find > its nomminated servers, but it gives up and just sits there not > synchronising time from any reference. So I have to remember to > manually "/etc/rc.d/ntpd restart" every time I reboot. > > So: does anyone know how to modify the boot-time order so that > svscan starts at (or before) the point in the boot cycle where > BIND would, on other systems? I suspect that it should be > possible by changing the PROVIDE: in svscan.sh to include one of > the things REQUIRE:'d by ntpd. Or perhaps the REQUIRE: LOGIN in > svscan.sh is incompatible with the BEFORE: LOGIN in ntpd? > > Has any other user of dnscache encountered and solved this > problem? > I use the following in svscan.sh, no problems with ntpdate or any other service: # PROVIDE: svscan # REQUIRE: FILESYSTEMS netif pf # BEFORE: routing - Max