[
https://issues.apache.org/jira/browse/BIGTOP-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569196#comment-13569196
]
Roman Shaposhnik commented on BIGTOP-838:
-----------------------------------------
Right, but that's what I'm saying -- we prefer that users utilize well know
locations for configuration files. In this particular case you can use
/etc/default/hadoop-<daemon name> to tweak location of the log files as easily
as you can with hadoop-env.sh.
The trouble with hadoop-env.sh is that it is extremely hadoop specific and
foreign to folks who don't have any Hadoop background.
> Both conf.empty and conf.pseudo packages don't seem to include a sample
> hadoop-env.sh file
> ------------------------------------------------------------------------------------------
>
> Key: BIGTOP-838
> URL: https://issues.apache.org/jira/browse/BIGTOP-838
> Project: Bigtop
> Issue Type: Improvement
> Components: General
> Affects Versions: 0.5.0
> Reporter: Harsh J
> Labels: conf, package
>
> As noticeable on
> https://git-wip-us.apache.org/repos/asf?p=bigtop.git;a=tree;f=bigtop-packages/src/common/hadoop/conf.pseudo;h=b0ca9e629fb6d51fb83c61f1354f4bbad155e3af;hb=HEAD,
> we should include a base hadoop-env.sh (and maybe a yarn-env.sh as well).
--
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