Bug 462575 - named query denied syslog messages lack information
Summary: named query denied syslog messages lack information
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: bind
Version: 4.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Adam Tkac
QA Contact:
URL:
Whiteboard:
Depends On: 241745
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-17 07:41 UTC by Adam Tkac
Modified: 2013-04-30 23:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-23 12:21:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Adam Tkac 2008-09-17 07:44:56 UTC
As written bellow RHBA-2008-0708 caused small regression with logging:

--- Additional comment from vogel on 2008-09-04 05:45:10 EDT ---

This patch apparently changes the logging category for this log message.

In prior versions, the "query (cache) denied" message would fall under the
"client" category, and the config entry

logging {
  category client { file "client_log"; };
};

would redirect this message away from syslog to a file.

With bind-9.2.4-30.el4, this stopped to work, and the message appears in
/var/log/messages instead.

Could you please change the patch so that it does not break the logging
configurability?

Comment 2 RHEL Program Management 2008-09-17 07:45:49 UTC
This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.

Comment 4 Adam Tkac 2010-02-23 12:21:50 UTC
Red Hat Enterprise Linux 4.9 update will contain only important, security and performance related fixes thus this issue won't be fixed in RHEL 4.

Note that bind in Red Hat Enterprise Linux 5 has same behavior as current ("broken") Red Hat Enterprise Linux 4 bind. This change is not Red Hat specific, it has been done by upstream developers.


Note You need to log in before you can comment on or make changes to this bug.