Date: Tue, 21 Nov 2017 09:45:27 +0300 From: Alexander Zagrebin <alex@zagrebin.ru> To: freebsd-net@freebsd.org Cc: Dag-Erling =?UTF-8?B?U23DuHJncmF2?= <des@des.no>, Andriy Gapon <avg@FreeBSD.org> Subject: Re: local_unbound, resolvconf, vpn Message-ID: <20171121094527.0952f3b9@vm2.home.zagrebin.ru> In-Reply-To: <86tvxp6jja.fsf@desk.des.no> References: <5689438f-6734-6b57-b700-d70ee2b7578a@FreeBSD.org> <86a7zq8er7.fsf@desk.des.no> <8a098542-9f04-3a41-76f1-e463e3e89c99@FreeBSD.org> <86y3n16mez.fsf@desk.des.no> <37f97bc5-5187-2700-5811-a9cf173eeb10@FreeBSD.org> <86tvxp6jja.fsf@desk.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi!
Also I have to notice that there is another issue with the default
local_unbound setup:
by default unbound uses syslog for logging, but usually the
local_unbound service starts before syslogd and so logging doesn't work
until local_unbound will be reloaded.
So it's looks reasonable to use logging to file by default.
As unbound runs in chroot, the log file has to be inside of
the /var/unbound directory, but now this directory contains a config
files.
I suggest to change the /var/unbound structure to be more hier(7)
friendly.
For example,
/var
/unbound
/etc - unbound configuration files
/conf.d - additional configuration files
/var
/log - unbound log files
--
Alexander Zagrebin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171121094527.0952f3b9>