From hdfs-issues-return-40222-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org Wed May 2 23:28:23 2012 Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E074E9239 for ; Wed, 2 May 2012 23:28:22 +0000 (UTC) Received: (qmail 53903 invoked by uid 500); 2 May 2012 23:28:22 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 53853 invoked by uid 500); 2 May 2012 23:28:22 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 53842 invoked by uid 99); 2 May 2012 23:28:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2012 23:28:22 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2012 23:28:21 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 38A7B42CA7B for ; Wed, 2 May 2012 23:28:01 +0000 (UTC) Date: Wed, 2 May 2012 23:28:01 +0000 (UTC) From: "Hudson (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <2045546870.19419.1336001281284.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <362960148.13609.1335889672706.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-3336) hdfs launcher script will be better off not special casing namenode command with regards to hadoop.security.logger MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267020#comment-13267020 ] Hudson commented on HDFS-3336: ------------------------------ Integrated in Hadoop-Hdfs-trunk-Commit #2249 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2249/]) HDFS-3336. hdfs launcher script will be better off not special casing namenode command with regards to hadoop.security.logger (rvs via tucu) (Revision 1333236) Result = SUCCESS tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1333236 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs > hdfs launcher script will be better off not special casing namenode command with regards to hadoop.security.logger > ------------------------------------------------------------------------------------------------------------------ > > Key: HDFS-3336 > URL: https://issues.apache.org/jira/browse/HDFS-3336 > Project: Hadoop HDFS > Issue Type: Bug > Components: scripts > Affects Versions: 0.23.1 > Reporter: Roman Shaposhnik > Assignee: Roman Shaposhnik > Priority: Minor > Fix For: 2.0.0 > > Attachments: HDFS-3336.patch.txt > > > All of the launcher scripts (except hdfs when called with a namenode argument) are defaulting to INFO,NullAppender setting for hadoop.security.logger. The only codepath where the default is INFO,RFAS is via hadoop-daemon.sh. This is exactly the right thing to do since only daemons are guaranteed to be executed under the proper user account (the one that has write/create access to the locations specified in ${hadoop.log.dir}/*). > It would be nice for 'hdfs namenode' to follow the suit and not produce spurious warnings about not being able to write to log locations when executed from under regular accounts. -- 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