Thanks; that does exactly what I need.

On Tue, Apr 16, 2019 at 11:33 AM <[email protected]> wrote:

> Hi,
>
> Try enabling asynchronous server start
> (https://www.knot-dns.cz/docs/2.8/html/reference.html#async-start)
> which reduces the delay between process start and control interface
> being active.
>
> Daniel
>
> On 2019-04-16 19:26, JCA wrote:
> > I have to integrate Knot in framework which will be testing for the
> > presence of a running instance of the Knot daemon by means of 'knotc
> > status'. This works fine, once knotd has loaded all the zones.
> > However, when launching it there will be a window of opportunity
> > during which 'knotc status' will fail, despite the fact that knotd is
> > already running, but still loading its zones.
> >
> > Two questions:
> >
> > 1. Is this a correct description, or am I missing something here?
> > 2. If it is right, is there a way, with the concourse of KNOT tools,
> > to find out whether knotd is already running or still loading zones?
> >
> > I guess that, if it is a matter of just verifying that knotd is
> > running, using the 'ps' command would be simpler. I wonder, however,
> > whether it can be done with KNOT tools alone.
>
-- 
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users

Reply via email to