[
https://issues.apache.org/jira/browse/CHUKWA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697100#action_12697100
]
Jerome Boulon commented on CHUKWA-104:
--------------------------------------
-1 forcing 644 is not the right way to do it
here what I think about setting permission in Chukwa Appender:
- use log4j to set permission to the log file, ex:
log4j.appender.CHUKWA.readPermission=
-- readPermission field not present in log4j, don't do anything, file
permission will use the default
-- readPermission field set to "All" then setReadable(true, false) otherwise
setReadable(true, true)
-- writePermission field not present in log4j, don't do anything, file
permission will use the default
-- writePermission field set to "All" then setWritable(true, false) otherwise
setReadable(true, true)
> Chukwa data collection depends on the permission of the log file
> ----------------------------------------------------------------
>
> Key: CHUKWA-104
> URL: https://issues.apache.org/jira/browse/CHUKWA-104
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: data collection
> Environment: Redhat 5.1, Java 6
> Reporter: Eric Yang
> Priority: Blocker
> Attachments: CHUKWA-104.patch
>
>
> In ChukwaDailyRollingAppender, the appender should set the file permission to
> be readable by ChukwaAgent. In this release, we are setting it to 644 to be
> sure that the log file can be collected by ChukwaAgent.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
