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

Harsh J commented on YARN-97:
-----------------------------

bq. It should be well documented for system not having bash installed by 
default such as FreeBSD.

Why don't we simply document requirements then?

I've recently seen /bin/sh shbanged scripts cause trouble on Ubuntu cause 
/bin/sh points to Ubuntu's dash (https://wiki.ubuntu.com/DashAsBinSh). You 
don't wanna run into such a trouble and end up changing things (hadoop or OS 
side) post-deploy.

I'll still vote we stick to one shell (bash) and be clear we need it.
                
> nodemanager depends on /bin/bash
> --------------------------------
>
>                 Key: YARN-97
>                 URL: https://issues.apache.org/jira/browse/YARN-97
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>         Environment: FreeBSD 8.2 / 64 bit
>            Reporter: Radim Kolar
>              Labels: patch
>         Attachments: bash-replace-by-sh.txt
>
>
> Currently nodemanager depends on bash shell. It should be well documented for 
> system not having bash installed by default such as FreeBSD. Because only 
> basic functionality of bash is used, probably changing bash to /bin/sh would 
> work enough.
> i found 2 cases:
> 1. DefaultContainerExecutor.java creates file with /bin/bash hardcoded in 
> writeLocalWrapperScript. (this needs bash in /bin)
> 2. yarn-hduser-nodemanager-ponto.amerinoc.com.log:2012-04-03 19:50:10,798 
> INFO org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: 
> launchContainer: [bash, -c, 
> /tmp/nm-local-dir/usercache/hduser/appcache/application_1333474251533_0002/container_1333474251533_0002_01_000012/default_container_executor.sh]
> this created script is also launched by bash - bash anywhere in path works - 
> in freebsd it is /usr/local/bin/bash

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

Reply via email to