accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-3450) Example logging configs should disable audit log to application log files
Date Wed, 24 Dec 2014 22:33:13 GMT


Josh Elser updated ACCUMULO-3450:
    Attachment: 0001-ACCUMULO-3450-Push-audit-configuration-into-Log4jCon.patch

I think this is all that's really required to fix this. Instead of only configuring the Audit
log once, re-configure the audit log when we configure the application logging.

This should also make it simple to roll auditLog.xml into more standard logging configuration

> Example logging configs should disable audit log to application log files
> -------------------------------------------------------------------------
>                 Key: ACCUMULO-3450
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: start
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 1.6.2, 1.7.0
>         Attachments: 0001-ACCUMULO-3450-Push-audit-configuration-into-Log4jCon.patch
> 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

View raw message