Uploaded image for project: 'CDH (READ-ONLY)'
  1. CDH (READ-ONLY)
  2. DISTRO-13

flume init.d scripts are not LSB compliant

          Details

          • Type: Bug
          • Status: Resolved
          • Priority: Major
          • Resolution: Fixed
          • Affects Version/s: CDH3b3, CDH3b4
          • Fix Version/s: CDH3u1
          • Component/s: Flume, Packaging
          • Labels:
            None
          • Environment:
            all linux

            Description

            Reposting here now that you are tracking. Third time is the charm I hope! Originally here: http://getsatisfaction.com/cloudera/topics/flume_init_d_scripts_are_not_lsb_compliant

            Posted this over here: https://issues.cloudera.org/browse/FLUME-100 but they bounced me back to this forum.

            From looking around I see there is another report on zookeeper's init.d scripts.

            Cloudera should really make all init.d scripts LSB compliant. See link below from my original jira:
            --------------------

            Most start/stop scripts in linux also support 'status' to see if the process is running.
            Can we add this to flume-master and flume-node init.d scripts?

            Here are the specs: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html

            Note that proper return codes should be returned so calls can be scripted or used with something like ha-linux that depend on proper codes.

              Attachments

                Activity

                  People

                  • Assignee:
                    bruno Bruno Mahé
                    Reporter:
                    shoffman Steve Hoffman
                  • Votes:
                    1 Vote for this issue
                    Watchers:
                    4 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: