You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2009/04/20 19:18:47 UTC
[jira] Commented: (CHUKWA-160) use log4j to set permission to the
log file
[ https://issues.apache.org/jira/browse/CHUKWA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700865#action_12700865 ]
Eric Yang commented on CHUKWA-160:
----------------------------------
The key words are somewhat confusing.
Does all mean user+others in unix?
Why don't we use the same keyword as unix file permission?
> use log4j to set permission to the log file
> -------------------------------------------
>
> Key: CHUKWA-160
> URL: https://issues.apache.org/jira/browse/CHUKWA-160
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: input tools
> Reporter: Jerome Boulon
>
> 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"
> * readPermission field set to "Group"
> * readPermission field set to "Owner only"
> * writePermission field not present in log4j, don't do anything, file permission will use the default
> * writePermission field set to "All"
> * writePermission field set to "Group"
> * writePermission field set to "Owner only"
> However, it seems not possible to set permission at the group level so this may be a potential issue that may force us to
> continue using chmod for specific case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.