From what I can see unbound init script is up-to-date. Do I need to add
override for the pidfile in unbound config? Even if I do that and it works, I
will still need to update the unbound init script as well so the easiest file
to me to update the init script to explicitly remove the pid file a
Shawn Zhou via Unbound-users wrote:
> I am running unbound 1.5.8 on ubuntu xenial. unbound doesn't run remove the
> pid file after it's stopped.
I believe the unbound packaging on Ubuntu xenial is old enough that it
still uses the sysv generator to create the service unit. You will
probably want
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
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
