[
https://issues.apache.org/jira/browse/HADOOP-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413213#comment-13413213
]
Devaraj Das commented on HADOOP-8552:
-------------------------------------
Hi Karthik, is this on the client or on the server side? (Guessing its on
client.. please confirm). In general, the audit log stuff doesn't make sense on
the client side. It's meant to be used on the server side only (and in
deployments I know about, the security audit logging is turned off on the
client side).
Your patch will work though. But I'll note that it might be introducing
compatibility issues due to the filename change of the log file (if someone is
collecting logs based on file names, etc.).
> Conflict: Same security.log.file for multiple users.
> -----------------------------------------------------
>
> Key: HADOOP-8552
> URL: https://issues.apache.org/jira/browse/HADOOP-8552
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf, security
> Affects Versions: 1.0.3, 2.0.0-alpha
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: HADOOP-8552_branch1.patch, HADOOP-8552_branch2.patch
>
>
> In log4j.properties, hadoop.security.log.file is set to SecurityAuth.audit.
> In the presence of multiple users, this can lead to a potential conflict.
> Adding username to the log file would avoid this scenario.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
