[
https://issues.apache.org/jira/browse/ACCUMULO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258440#comment-14258440
]
Christopher Tubbs commented on ACCUMULO-3450:
---------------------------------------------
Personally, I'd like to see the {{auditLog.xml}} file go away completely, and
just put the log rules for auditing in the normal log configuration. As is, our
logging is complex enough (and that's not even including tracing, which is a
specialized kind of logging). We also definitely should not be initializing the
logging system twice, with two different files, in the same JVM. That does not
seem to be correct usage.
(Ideally, I think we shouldn't be initializing the log system in code anyway,
we should rely on slf4j/log4j to initialize itself with standard log files,
{{log4j.xml}} and/or {{log4j.properties}}, and work within that constraint, but
that's a whole separate issue.)
> Example logging configs should disable audit log to application log files
> -------------------------------------------------------------------------
>
> Key: ACCUMULO-3450
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3450
> Project: Accumulo
> Issue Type: Bug
> Components: start
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Trivial
> Fix For: 1.7.0
>
>
> The presence of an auditLog.xml file controls the "audit" log for incoming
> clients, security operations, etc. Because a normal logger instance is used
> for this purpose, it also gets dumped into the normal application log files
> (e.g. $process_$host.[debug.]log).
> We should turn off the audit log in the generic_logger configuration and let
> auditLog.xml create the log file specifically for audits when the user
> configures it as such (as the audit log is intended to be off by default by
> virtue of the example configuration files we generate).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
