On Wed, May 15, 2019 at 10:39 AM Sven Joachim wrote:
> I am not really familiar with apparmor or resolvconf, but in
> /etc/apparmor.d/usr.sbin.named I found the following:
>
> ,
> | # support for resolvconf
> | /{,var/}run/named/named.options r,
> `
>
> which suggests that the
I also have a similar problem accessing /run/named. bind can't create the
directory or any files in it. The error messages:
couldn't mkdir '//run/named': Permission denied
could not create //run/named/session.key
Apparmor problems can be fixed by running aa-logprof and selecting the best
On 2019-05-15 09:33 -0700, Ross Boylan wrote:
> Sven, thanks for the tip about AppArmor. Yet another presumably
> complicated system I've avoided learning about til now. I guess it's
> time.
>
> As to why bind is trying to open /run/named/named.resolvers: that is a
> customized integration with
On Wed, May 15, 2019 at 12:11:58PM -0400, Lee wrote:
> The way I fixed my permission problems after telling bind to log to a
> file instead of syslog was
> su -
> to become root
> su bind
> which didn't work because
> # grep bind /etc/passwd
> bind:x:116:119::/var/cache/bind:/bin/false
>
Sven, thanks for the tip about AppArmor. Yet another presumably
complicated system I've avoided learning about til now. I guess it's
time.
As to why bind is trying to open /run/named/named.resolvers: that is a
customized integration with resolvconf. It is not the default, but it
is something I
On 5/15/19, Ross Boylan wrote:
> I have a new buster system with a bind setup based on (much) older*
> systems, on which it worked fine. On buster, it doesn't.
> In two different places in my configuration I referred to files or
> directories that were outside of bind proper, and in both cases
On 2019-05-14 21:50 -0700, Ross Boylan wrote:
> I have a new buster system with a bind setup based on (much) older*
> systems, on which it worked fine. On buster, it doesn't.
> In two different places in my configuration I referred to files or
> directories that were outside of bind proper, and
I have a new buster system with a bind setup based on (much) older*
systems, on which it worked fine. On buster, it doesn't.
In two different places in my configuration I referred to files or
directories that were outside of bind proper, and in both cases this
failed with permission problems.
I'm
8 matches
Mail list logo
