incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <j...@apache.org>
Subject [jira] [Created] (BIGTOP-571) we might need to guard against direct use of the upstream launcher scripts
Date Wed, 02 May 2012 17:58:48 GMT
Roman Shaposhnik created BIGTOP-571:
---------------------------------------

             Summary: we might need to guard against direct use of the upstream launcher scripts
                 Key: BIGTOP-571
                 URL: https://issues.apache.org/jira/browse/BIGTOP-571
             Project: Bigtop
          Issue Type: Improvement
          Components: General
    Affects Versions: 0.4.0
            Reporter: Roman Shaposhnik
            Assignee: Roman Shaposhnik
             Fix For: 0.4.0


I've noticed lately that new users of the Bigtop distro fall prey
to thinking that they can simply utilized upstream launcher scripts
as is by running them from under /usr/lib/<component>bin
directories. Something this works. More often it doesn't.
For example, in order for the hadoop scripts to work the users
actually need to
  export  HADOOP_LIBEXEC_DIR
properly.

In case of Zookeeper there's more stuff to be setup in the env.
before you can actually execute upstream scripts.

Most of these issues have to do with a tendency of upstream
scripts to cater to the dev. environment where keeping logs, etc.
in /tmp is perfectly fine. For Bigtop we have to override that and
the place we do that is in /usr/bin/<component> launcher
scripts.

The proposal that was discussed on the list is to at least disable
an executable bit on these scripts so that casual users can't execute
them accidentally.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message