[
https://issues.apache.org/jira/browse/ACCUMULO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258514#comment-14258514
]
Josh Elser commented on ACCUMULO-3450:
--------------------------------------
Oh interesting, I wonder if I broke things with this the last time I was
working on the dynamic log-forwarding to the monitor. Thanks for digging into
this, Keith.
MonitorLog4jWatcher is both a file watchdog (for the configured log4j
configuration file: xml or properties) and a ZK watcher. It will refresh the
logging subsystem as necessary to make sure the changes are observed. It seems
likely that the auditLog.xml configuration would also need to be added after
the subsystem is re-initialized.
> 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)
