You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2013/02/12 20:35:13 UTC
[jira] [Commented] (BIGTOP-504) provide a functionality for
detecting libjvm.so in bigtop-utils
[ https://issues.apache.org/jira/browse/BIGTOP-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576925#comment-13576925 ]
Sean Mackrory commented on BIGTOP-504:
--------------------------------------
Bruno - I didn't see this JIRA before, and I recently started working on BIGTOP-845 and some other changes to bigtop-utils. Have you already worked on this, or do you mind if I take it over? Just didn't want to step on any toes or duplicate work.
> provide a functionality for detecting libjvm.so in bigtop-utils
> ---------------------------------------------------------------
>
> Key: BIGTOP-504
> URL: https://issues.apache.org/jira/browse/BIGTOP-504
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Bruno Mahé
> Fix For: 0.6.0
>
>
> Currently, for hdfs fuse we have code lile this in the launcher script:
> {noformat}
> if [ "\${LD_LIBRARY_PATH}" = "" ]; then
> export LD_LIBRARY_PATH=/usr/lib
> for f in \`find \${JAVA_HOME}/jre/lib -name client -prune -o -name libjvm.so -exec dirname {} \;\`; do
> export LD_LIBRARY_PATH=\$f:\${LD_LIBRARY_PATH}
> done
> fi
> {noformat}
> It would be nice to provide this as a general purpose detection code in bigtop-utils.
--
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