Date: Tue, 17 Jan 2023 09:11:16 -0800 From: User Ngor <ihor@antonovs.family> To: freebsd-current@freebsd.org Subject: Re: local-unbound regression Message-ID: <50ca9367-f2dc-8634-403b-c6fd033b0ddf@antonovs.family> In-Reply-To: <6d204b08-5f67-6a0c-4982-93c5f9da8bf5@antonovs.family> References: <6d204b08-5f67-6a0c-4982-93c5f9da8bf5@antonovs.family>
next in thread | previous in thread | raw e-mail | index | archive | help
I discovered that recent unbound update broke my VPN scripts, after some investigation I think I found the problem - default location of the config file was reset to upstream value. My config file is at /var/unbound/unbound.conf (as created by local-unbound-setup) but when I use local-unbound-control I see this error message: > > > # local-unbound-control flush_stats > [1673972554] unbound-control[16206:0] error: Could not open > /usr/local/etc/unbound/unbound.conf: No such file or directory > [1673972554] unbound-control[16206:0] fatal error: could not read > config file > > I have not yet created bugzilla bug > https://cgit.freebsd.org/src/commit/?id=1838dec31895fd4752fa8631322ab93be0705a66 /* Pathname to the Unbound configuration file */ -#define CONFIGFILE "/var/unbound/unbound.conf" +#define CONFIGFILE "/usr/local/etc/unbound/unbound.conf" It looks like it was intentional, but then my local-unbound-setup keeps creating configuration in the old destination... And it looks like a POLA violation - I can imagine lot's of users might have configs in /var/unbound -- Ihor Antonov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50ca9367-f2dc-8634-403b-c6fd033b0ddf>