[jira] [Issue Comment Deleted] (ACCUMULO-3450) Example logging configs should disable audit log to application log files

["Josh Elser (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated ACCUMULO-3450:
---------------------------------
    Comment: was deleted

(was: Sure, that's fine by me -- the "non-standardness" of our logging infrastructure setup has been pointed out as "awkward" before.

I'm just looking to make a small fix to prevent Audit from going to the application logs when the configuration has specifically said that auditing should be off.

Let's open a ticket specifically to track the above concerns since I imagine it will take some thought and consideration.)

> 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)