[ https://issues.apache.org/jira/browse/HADOOP-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078614#comment-14078614 ]
Allen Wittenauer commented on HADOOP-6590: ------------------------------------------ I might pick this one back up after HADOOP-9902 gets committed. I was actually thinking about this problem, especially since we specify the user that secure data nodes are supposed to run as... why not do the same for the other services? > 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 was sent by Atlassian JIRA (v6.2#6252)