You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2014/11/05 11:08:34 UTC

[jira] [Resolved] (FLUME-581) It would be very desirable for flume to follow the rest of CDH components and keep flume-env.sh in /etc

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

Ashish Paliwal resolved FLUME-581.
----------------------------------
       Resolution: Won't Fix
    Fix Version/s: v0.9.5

Won't fix. 0.X branch not maintained anymore

> It would be very desirable for flume to follow the rest of CDH components and keep flume-env.sh in /etc
> -------------------------------------------------------------------------------------------------------
>
>                 Key: FLUME-581
>                 URL: https://issues.apache.org/jira/browse/FLUME-581
>             Project: Flume
>          Issue Type: Improvement
>    Affects Versions: v0.9.4
>            Reporter: Disabled imported user
>            Priority: Minor
>             Fix For: v0.9.5
>
>
> Currently, flume looks for flume-env.sh down at /usr/lib/flume/bin. It really makes more sense to treat flume-env.sh as a config file and thus keep it in /etc/flume (plus mark it as %config for packaging purposes)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)