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

Hadoop QA commented on HADOOP-6590:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12449308/HADOOP-6590-2010-07-12.txt
  against trunk revision 1071364.

    +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.

    -1 patch.  The patch command could not apply the patch.

Console output: 
https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/278//console

This message is automatically generated.

> Add a username check in hadoop-daemon.sh
> ----------------------------------------
>
>                 Key: HADOOP-6590
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6590
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: scripts
>    Affects Versions: 0.22.0
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>            Priority: Minor
>         Attachments: HADOOP-6590-2010-07-12.txt, HADOOP-6590.patch
>
>
> We experienced a case that sometimes we accidentally started HDFS or 
> MAPREDUCE with root user. Then the directory permission will be modified and 
> we have to chown them. It will be nice if there can be a username checking in 
> the hadoop-daemon.sh script so that we always start with the desired username.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to