incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (Commented) (JIRA)" <>
Subject [jira] [Commented] (BIGTOP-510) log4j property must be set with property in for Flume NG pkg
Date Wed, 04 Apr 2012 03:59:19 GMT


Roman Shaposhnik commented on BIGTOP-510:

Wouldn't it be possible to parameterize upstream in such a way that it would
allow overrides from the command line via -Dfoo=bar ? We do it for most of the components
and it works fine without changing the content of the upstream file.
> log4j property must be set with property in for Flume NG pkg
> ------------------------------------------------------------
>                 Key: BIGTOP-510
>                 URL:
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.3.0
>         Environment: [CentOS 5.7 64-bit]
>            Reporter: Will McQueen
>            Assignee: Bruno Mahé
>             Fix For: 0.3.0
> The /etc/flume-ng/ file is configured by default to write to the current
dir, which causes perms issues when the /etc/init.d/flume-ng-node daemon (running as user
'flume') attempts to write it. A fix would be to provide so that the property's
value specifies /var/log/flume-ng as the log dir, like this:
>      flume.log.dir=/var/log/flume-ng
> Thank you.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message