Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 12 Jul 2012 00:17:34 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <1867504383.39218.1342052254403.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <12287512.955.1341354154974.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HADOOP-8552) Conflict: Same security.log.file for
 multiple users.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karthik Kambatla updated HADOOP-8552:
-------------------------------------

    Attachment: HADOOP-8552_branch1.patch

Updating the patch after testing.

Tested it on a secure cluster, and the appropriate log file is created.
                
> 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