You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2013/03/26 19:25:15 UTC

[jira] [Updated] (BIGTOP-566) Flume NG pkg init script should allow user to customize the location of the conf dir

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

Roman Shaposhnik updated BIGTOP-566:
------------------------------------

    Fix Version/s:     (was: 0.6.0)
    
> Flume NG pkg init script should allow user to customize the location of the conf dir
> ------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-566
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-566
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>         Environment: all
>            Reporter: Will McQueen
>            Assignee: Bruno Mahé
>         Attachments: BIGTOP-566.patch, BIGTOP-566.patch
>
>
> A typical Flume NG invocation is:
>      bin/flume-ng --conf-file conf/flume-conf.properties.template  --conf conf --name agent1
> ...and the corresponding invocation after installing the Flume NG bigtop package would be:
>      /usr/lib/flume-ng/bin/flume-ng --conf-file /etc/flume-ng/conf/flume.conf --conf /etc/flume-ng/conf --name agent
> The Flume NG init script, installed as part of Bigtop Flume NG, allows us to modify:
> 1) the --conf-file value (via FLUME_CONF_FILE)
> 2) the --name value (via FLUME_AGENT_NAME)
> ...but not the --conf value. So the user loses some flexibility when using Bigtop Flume NG over Apache Flume NG.
> I recommend that the /etc/init.d/flume-ng-agent script be modified to allow the user to set FLUME_CONF_DIR. That is, in this init script, please change this:
>      FLUME_CONF_DIR=/etc/flume-ng/conf
> ..to this:
>      FLUME_CONF_DIR=${FLUME_CONF_DIR:-/etc/flume-ng/conf}

--
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