Bigtop
  1. Bigtop
  2. BIGTOP-571

we might need to guard against direct use of the upstream launcher scripts

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.4.0
    • Fix Version/s: None
    • Component/s: General
    • Labels:
      None

      Description

      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.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Roman Shaposhnik
            Reporter:
            Roman Shaposhnik
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development