Caching in libunbound

Rick van Rein rick at
Thu Mar 21 12:16:16 UTC 2019


I was thinking that Unbound might merge processes...

> However, the hope
> I had was that since Unbound == Unbound it might trust itself and allow
> two streams of requests to come together.

...because it fork()ed a process in the background, which I assumed
might be a shared Unbound daemon.

Apparently this is just to service query/responses.  Unexpected, as I
had setup an event loop and was tidily calling ub_process() and
receiving its callbacks.

To be honest, I don't really understand why Unbound doesn't have a modus
operandi that supports event loops without thread or process!


More information about the Unbound-users mailing list