Description of problem: default logfile in named.conf breaks with logrotate settings.

In the default named conf:

logging {
        channel default_debug {
                file "data/named.run";
                severity dynamic;
        };
};

In /etc/logrotate.d/named:

/var/log/named.log {
    missingok
    create 0644 named named
    postrotate
        /sbin/service named reload  2> /dev/null > /dev/null || true
    endscript
}

In a chrooted environment, named doesn't write to /var/log/named.log but instead it writes in /var/named/chroot/var/named/data/named.run.

This file is growing and growing (especially when on the same machine tools like spamassassin are being used to filter spam messages).

The weird thing is that everything is being logged twice: first every lookup failure is being written in the /var/log/messages (which really makes it hard to see other non-named messages in the messages log) and second it also is written in the /var/named/chroot/var/named/data/named.run file.

In my opinion it should really not be necessary to write named info on two places at the same time.

Because the information from the debug channel in /var/named/chroot/var/named/data/named.run is not being time-stamped, I would think the best approach here is to disable the debug channel in named.conf and to adapt rsyslog's configuration to redirect named messages from the system messages log to the /var/log/named.log file. this would also fix the broken logrotate configuration for named.


Version-Release number of selected component (if applicable):

bind-libs-9.5.1-1.P1.fc10.i386
bind-utils-9.5.1-1.P1.fc10.i386
bind-9.5.1-1.P1.fc10.i386
bind-chroot-9.5.1-1.P1.fc10.i386
logrotate-3.7.7-1.fc10.i386



How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: