Date: Fri, 12 Dec 2014 05:00:00 -0600 From: Scot Hetzel <swhetzel@gmail.com> To: FreeBSD Ports <freebsd-ports@freebsd.org> Cc: Matt Smith <fbsd@xtaz.co.uk> Subject: Re: Unbound/NSD rc startup order Message-ID: <CACdU%2Bf8ECBJr4VrLXhu1%2BKJfnq5=%2BWdFqm8DAZn5S_TUAFxJqw@mail.gmail.com> In-Reply-To: <548AC04A.8000804@bluerosetech.com> References: <20141211105139.GA1270@xtaz.uk> <20141212075328.GB52267@xtaz.uk> <548AC04A.8000804@bluerosetech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 12, 2014 at 4:15 AM, Darren Pilgrim <list_freebsd@bluerosetech.com> wrote > On 12/11/2014 11:53 PM, Matt Smith wrote: >> >> Somebody has let me know that I made an obvious mistake in the above. I >> meant that the default rcorder is to run Unbound first followed by NSD. >> So to clarify I think in the default situation Unbound starts first, >> contacts NSD and gets no answer because it hasn't been started yet and >> then fails in some way. Whereas if NSD is running first then Unbound is >> happy. > > > Unbound requires SERVERS, but nsd requires LOGIN, a much later checkpoint. > > The fix would be adding an rcorder override mechanism whereby one could > specify additional constraints (like unbound REQUIRE nsd). If there's > interest for this, I can see about a patch. > Would it be better to add: # BEFORE: unbound to the dns/nsd rc.d script? -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACdU%2Bf8ECBJr4VrLXhu1%2BKJfnq5=%2BWdFqm8DAZn5S_TUAFxJqw>