Date: Wed, 8 Nov 2017 15:17:13 +0300 From: Alexander Zagrebin <alex@zagrebin.ru> To: freebsd-net@freebsd.org Subject: Re: local_unbound, resolvconf, vpn Message-ID: <20171108151713.413d28c4@vm2.home.zagrebin.ru> In-Reply-To: <5689438f-6734-6b57-b700-d70ee2b7578a@FreeBSD.org> References: <5689438f-6734-6b57-b700-d70ee2b7578a@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
В Wed, 8 Nov 2017 13:38:28 +0200
Andriy Gapon <avg@FreeBSD.org> пишет:
> I've just enabled local_unbound on a machine and everything seems to
> work fine. But there are a few minor quirks that I would like to
> report.
> Last. Every time I connect to a VPN (via vpnc or openvpn, for
> exmaple) the unbound daemon is restarted. That's expected because
> its configuration is changed. But there is a slightly annoying
> message that appears to be harmless: unbound: [7457:0] error: cannot
> chdir to directory: (No such file or directory)
>
> I wonder what causes this messages and if it's possible to shut it up.
This message appears because you are using chroot.
You have to edit /var/unbound/unbound.conf and add a trailing slash to
value of the 'directory' parameter:
server:
...
chroot: /var/unbound
directory: /var/unbound/
...
When unbound uses chroot, it determines the directory name, that it will
be use for chdir call, taking in account the value of 'chroot'
parameter. If 'chroot' equals 'directory' the unbound will call
chdir(''), which will cause an error.
--
Alexander Zagrebin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171108151713.413d28c4>