Hello,
An ubuntu user also ran into this problem [1] as well so I revisited the
patch and turned it into a merge request [2]. I tested the code with
Unbound 1.10.1-1 and chroot set to /var/lib/unbound.
Regards,
Simon
1: https://bugs.launchpad.net/bugs/1885907
2:
Hello Timo,
On 2018-11-09 8:13 a.m., Timo Sigurdsson wrote:
> However, I believe the patch is not fully correct. With the proposed
> patch, mounting of the notify socket is done unter the condition that
> $CHROOT_DIR and $UNBOUND_BASE_DIR are *not* equal. This means that
> the socket will not be
Hi,
I would like to chime in here and second the request of exposing the systemd
notify socket inside the chroot.
However, I believe the patch is not fully correct. With the proposed patch,
mounting of the notify socket is done unter the condition that $CHROOT_DIR and
$UNBOUND_BASE_DIR are
Package: unbound
Version: 1.6.4-1
With the new systemd service using Type=notify, the chroot setup needs
to mount bind the systemd notify socket in the chroot and umount it on
service stop. Please find a patch that does that.
Regards,
Simon
commit e4ae81cbf04194cea140ce4966b701449b5f823a
Author:
4 matches
Mail list logo
