[jira] [Commented] (BIGTOP-1159) /usr/lib/flume-ng/plugins.d/ needs to be created and owned by flume

["Bruno Mahé (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081580#comment-14081580 ] 

Bruno Mahé commented on BIGTOP-1159:
------------------------------------

I actually never thought about using unpackaged plugins :)

So we could look into implementing both:
* /usr/lib/flume-ng/plugins.d/ for packaged ones
* /var/lib/flume-ng/plugins.d/ for whoever does not want to package their plugins.

At the end of the day, it's just a path on the classpath. So it does not have to be either way.
After looking at the Apache Flume binary, it appears to accept as parameters a list of plugins directory. So we can definitely implement it in another ticket.

> /usr/lib/flume-ng/plugins.d/ needs to be created and owned by flume
> -------------------------------------------------------------------
>
>                 Key: BIGTOP-1159
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1159
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Bruno Mahé
>            Assignee: Bruno Mahé
>         Attachments: 0001-BIGTOP-1159.-usr-lib-flume-ng-plugins.d-needs-to-be-.patch
>
>
> Apache Flume expects plugins to be dropped in /usr/lib/flume-ng/plugins.d/.
> But our package do not provide such directory since flume does not ship any plugin.
> Apache Flume package should create an empty directory /usr/lib/flume-ng/plugins.d/ and owned it.
> So plugins can be dropped automatically as packages into their own subdirectories.



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