[jira] [Updated] (BIGTOP-1266) Zookeeper init script doesn't source /etc/default/zookeeper

["Sean Mackrory (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BIGTOP-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Mackrory updated BIGTOP-1266:
----------------------------------

    Attachment: 0001-BIGTOP-1266.-Zookeeper-init-script-doesn-t-source-et.patch

Patch attached. ZooKeeper seems ripe for migration to the new init script template, as there are 3 copies.

[~fwiffo] - most of the services also have an /etc/default file that gets installed with the package that contains some sensible defaults, or at least a few commented-out examples of common tweaks. It would be good to do that now, so that the file can be managed as a configuration file during upgrades. Adding this file later would conflict with anything the user has added manually. Any suggestions on the common tweaks for ZooKeeper we should have in there?

> Zookeeper init script doesn't source /etc/default/zookeeper
> -----------------------------------------------------------
>
>                 Key: BIGTOP-1266
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1266
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Joey Echeverria
>         Attachments: 0001-BIGTOP-1266.-Zookeeper-init-script-doesn-t-source-et.patch
>
>
> Most of the service scripts source /etc/default/<daemon>, but Zookeeper doesn't. This makes it cumbersome to set environment variables for the Zookeeper daemons.



--
This message was sent by Atlassian JIRA
(v6.2#6252)