Red Hat Bugzilla – Bug 41391
Ownership conflict in "named.log" rotation
Last modified: 2007-04-18 12:33:20 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2smp i686; en-US; 0.7)
Description of problem:
File "/etc/logrotate.d/named" is used to rotate BIND's log file, specified
as "/var/log/named.log". This log file cannot exist, though, because BIND
(user=named, group=named) cannot write to the specified "/var/log" directory.
Steps to Reproduce:
1. Install bind-9.1.0-10 RPM.
Actual Results: Installation of this RPM installs the file
"/etc/logrotate.d/named"; it creates the user "named" and the group
"named"; it installs the BIND startup script with runs named with the
newly-created user & group identities.
Hello? The bug has been New for over two weeks.
I noticed this to - but I don't see the problem - log rotate works? Why is this
Perhaps I expressed my self badly. Logrotate will indeed rotate named.log. The
problem is named cannot write the logfile to be rotated.
The named daemon, running as user and group "named" cannot write to /var/log
because that directory is owned by "root". Thus the file "/var/log/named.log"
which logrotate will attempt to rotate cannot exist because named cannot write
To sum up: there is no problem with the behavior of logrotate. The problem is
that bind cannot write to "/var/log/named.log".
Can you please test the latest bind package from rawhide (9.2.1-6)
which will be available in rawhide soon ?
I think this is fixed now, but would like to get confirmation.
Four years later: it seems to be fixed. Please close this issue.
This BZ was in "MODIFIED" state meaning that changes had gone in for it; the
bug reporter is then expected to close as CURRENTRELEASE / RAWHIDE once the
fix is verified.
Now closing - thank you.