03.10.2014 20:52, Robert Edmonds wrote:
> Hi, Michael:
>
> Michael Tokarev wrote:
[]
> Hm, this directory is chown'd to unbound:unbound in the postinst. [...]
So, you chown /var/lib/unbound and run unbound-anchor as root both in postinst
and in the startup script. And unbound-anchor is not real
03.10.2014 20:52, Robert Edmonds wrote:
> Hi, Michael:
>
> Michael Tokarev wrote:
>> unbound server logs a warning like this:
>>
>> unbound[616]: [616:0] error: could not open autotrust file for writing,
>> /var/lib/unbound/root.key.616-0: Permission denied
[]
>> Note that while the unbound.conf
Hi, Michael:
Michael Tokarev wrote:
> unbound server logs a warning like this:
>
> unbound[616]: [616:0] error: could not open autotrust file for writing,
> /var/lib/unbound/root.key.616-0: Permission denied
>
> apparently unbound daemon (not only unbound-anchor) tries to write
> auto-trust-an
Package: unbound
Version: 1.4.22-2
Severity: normal
unbound server logs a warning like this:
unbound[616]: [616:0] error: could not open autotrust file for writing,
/var/lib/unbound/root.key.616-0: Permission denied
apparently unbound daemon (not only unbound-anchor) tries to write
auto-trust-
4 matches
Mail list logo
