Re: local-unbound regression

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