Hi Shawn,
Unbound tries to remove the pidfile on exit. It also tries to chown it,
if the username is set in unbound.conf.
Also if the pidfile is not located inside the chroot, then unbound
cannot remove the pidfile itself.
Best regards, Wouter
On 07/03/18 03:03, Shawn Zhou via Unbound-users wr
Am 06.03.2018 um 11:02 schrieb W.C.A. Wijngaards via Unbound-users:
> Unbound 1.7.0rc1 maintainers prerelease is available
Hello Wouter,
the feature list sounds promising!
3 points:
1.
contrib/fastrpz.patch apply but not without additional help from patch
I have a "fixed" version that apply wi
Hi,
I am running unbound 1.5.8 on ubuntu xenial. unbound doesn't run remove the pid
file after it's stopped. I was expecting the pid file should be owned by
unbound user as otherwise unbound probably wouldn't be able to remove it;
however, I didn't see any permission errors from unbound logs. I
Hi,
Unbound 1.7.0rc1 maintainers prerelease is available:
https://www.unbound.net/downloads/unbound-1.7.0rc1.tar.gz
sha256 eb9e57e44f7bb6e68879c8672c9a9b15273cece250d1ed85964b9620e736521a
pgp https://www.unbound.net/downloads/unbound-1.7.0rc1.tar.gz.asc
This release adds authority zones, for a lo
Hi,
Yes the key files are platform independent.
Best regards, Wouter
On 06/03/18 06:54, SIMON BABY via Unbound-users wrote:
> Hello Paul,
>
> Thank for looking into my issue. Yes, Am cross compiling for the
> target. Below is my configuration logs. I am implementing the client
> resolver appl
