[
https://issues.apache.org/jira/browse/FLUME-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577260#comment-13577260
]
Dimitri Krassovski commented on FLUME-767:
------------------------------------------
Would it not make sense to prefix all java invocations with $JAVA_HOME/bin in
the script?
I did this on my production boxes, because I have a mixed 6/7 java environment.
First I assumed that setting JAVA_HOME would select the right version to be
used by flume, but that just loaded some jars from jre6, while java itself was
jre7.
> 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
>
> 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 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
