[
https://issues.apache.org/jira/browse/FLUME-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal resolved FLUME-767.
----------------------------------
Resolution: Won't Fix
Fix Version/s: v0.9.5
Won't fix. 0.X branch not maintained anymore
> The bin/flume script assumes that Java exists in the $PATH variable despite
> the existence of $JAVA_HOME
> -------------------------------------------------------------------------------------------------------
>
> Key: FLUME-767
> URL: https://issues.apache.org/jira/browse/FLUME-767
> Project: Flume
> Issue Type: Bug
> Components: Shell
> Affects Versions: v0.9.2, v0.9.4
> Environment: RHEL6, OS X
> Reporter: John Ryding
> Assignee: Alexander Alten-Lorenz
> Priority: Minor
> Fix For: v0.9.5
>
>
> I am creating a set of scripts that will automatically install Flume and all
> of its dependencies. These scripts end up installing Java from a tar archive
> and do not place Java on the environment's PATH. I am encountering a problem
> in the bin/flume script with the following line:
> exec $NODE_WATCHDOG java $JOPTS $UOPTS com.cloudera.flume.agent.FlumeNode "$@"
> This command assumes that Java is set in the $PATH variable despite the
> existence of $JAVA_HOME. The bin/flume script should be updated to not rely
> on Java being placed in the PATH environment variable:
> exec $NODE_WATCHDOG $JAVA_HOME/bin/java $JOPTS $UOPTS
> com.cloudera.flume.agent.FlumeNode "$@"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
