[
https://issues.apache.org/jira/browse/HADOOP-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489876#comment-13489876
]
Chris Nauroth commented on HADOOP-9005:
---------------------------------------
2. I see lines like this in hadoop-env.sh. It seems audit logger is disabled
instead of security logger.
{code}
export
HADOOP_NAMENODE_OPTS="-Dhadoop.security.logger=${HADOOP_SECURITY_LOGGER:-INFO,RFAS}
-Dhdfs.audit.logger=${HDFS_AUDIT_LOGGER:-INFO,NullAppender}
$HADOOP_NAMENODE_OPTS"
export
HADOOP_SECONDARYNAMENODE_OPTS="-Dhadoop.security.logger=${HADOOP_SECURITY_LOGGER:-INFO,RFAS}
-Dhdfs.audit.logger=${HDFS_AUDIT_LOGGER:-INFO,NullAppender}
$HADOOP_SECONDARYNAMENODE_OPTS"
{code}
3. Most of the variables look to be set up with commented out lines for people
to uncomment and use. i.e.:
{code}
@rem Extra Java CLASSPATH elements. Automatically insert capacity-scheduler.
@rem set HADOOP_CLASSPATH=
{code}
I noticed that there is no equivalent "@rem set JAVA_HOME" line.
> Merge hadoop cmd line scripts from branch-1-win
> -----------------------------------------------
>
> Key: HADOOP-9005
> URL: https://issues.apache.org/jira/browse/HADOOP-9005
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: trunk-win
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-9005.branch-trunk-win.scripts.2.patch,
> HADOOP-9005.branch-trunk-win.scripts.3.patch,
> HADOOP-9005.branch-trunk-win.scripts.4.patch,
> HADOOP-9005.branch-trunk-win.scripts.5.patch,
> HADOOP-9005.branch-trunk-win.scripts.6.patch,
> HADOOP-9005.branch-trunk-win.scripts.patch
>
>
> Tracking Jira for merging hadoop cmd line scripts from branch-1-win to trunk.
> Scripts also have to be updated to reflect their unix equivalents.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
