logging permission denied
blrmaani
blrmaani at gmail.com
Wed Sep 10 16:26:01 UTC 2008
File is relative to chroot dir. modify file "/var/log/named/named.log"
to reflect this change and retry.
On Sep 10, 11:28 am, "aklist" <aklist_b... at enigmedia.com> wrote:
> Hi All: I reinstalled bind to 9.5.0-p1 last month, and it's now running
> chrooted (it wasn't before).
>
> My existing config file's logging statement looks like:
>
> logging {channel "my_syslog" { syslog daemon; severity info; };
> channel "my_file" { file "/var/log/named/named.log" versions 3 size
> 1000k;
> severity dynamic;
> print-category yes;
> print-severity yes;
> print-time yes; };
> channel "null" { null; };
> category "default" { "my_syslog"; "my_file"; "my_stats"; };
> category "general" { "my_file"; "my_stats"; };
> category "notify" { "my_file"; };
> category "queries" { "my_file"; };
> category "unmatched" { "null"; "my_stats"; };
> category "xfer-out" { "my_file"; };
> channel "my_stats" { file "/var/log/named/namedstats.log" versions 3
> size 100k;
> severity dynamic;
> print-category yes;
> print-severity yes;
> print-time yes; };
>
> };
>
> but when I reload bind I see that the "mystats" and "my_file" can't be
> written with permission denied. Do I need to edit my config to target the
> chroot, or do I need to edit the permissions on the existing directories to
> allow BIND to write the logs?
>
> TIA
More information about the bind-users
mailing list