Unbound does not remove pid file outside chroot directory when terminated about unbound

[ralphdolmans]

Thanks for your report. Removing the pidfile is not possible as privileges are dropped after the creation of this file.

NSD does not allow a pidfile outside of the chroot directory. Adding this requirement to Unbound is not desirable as this will break current installations. Note that Unbound should not have a problem on startup with an old pidfile present. If no process is running with the PID from the file Unbound will only log the "did not exit gracefully last time" message when the pidfile is in chroot, for exactly this reason.

If have added text to the ubound.conf man page to reflect this limitation.