[
https://issues.apache.org/jira/browse/BIGTOP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245939#comment-13245939
]
Mike Percy commented on BIGTOP-510:
-----------------------------------
Maybe we can just cd /var/log/flume-ng instead of replacing the file. I'm
concerned about not being able to gracefully incorporate changes to the logger
defaults across Flume releases if we do a complete replacement.
> log4j property must be set with property in for Flume NG pkg
> ------------------------------------------------------------
>
> Key: BIGTOP-510
> URL: https://issues.apache.org/jira/browse/BIGTOP-510
> 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/log4j.properties 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 log4j.properties 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
