[ 
https://issues.apache.org/jira/browse/HADOOP-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408546#comment-13408546
 ] 

Hadoop QA commented on HADOOP-8552:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12535000/HADOOP-8552_branch2.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified 
tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1180//console

This message is automatically generated.
                
> 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

        

Reply via email to