[
https://issues.apache.org/jira/browse/HADOOP-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661266#action_12661266
]
Hudson commented on HADOOP-4268:
--------------------------------
Integrated in Hadoop-trunk #708 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/708/])
. Change fsck to use ClientProtocol methods for enforcing permissions.
(szetszwo)
> Permission checking in fsck
> ---------------------------
>
> Key: HADOOP-4268
> URL: https://issues.apache.org/jira/browse/HADOOP-4268
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.17.2
> Reporter: Koji Noguchi
> Assignee: Tsz Wo (Nicholas), SZE
> Fix For: 0.21.0
>
> Attachments: 4268_20081217.patch, 4268_20081218.patch,
> 4268_20081218b.patch, 4268_20081230.patch
>
>
> Quoting from HADOOP-3222 ("fsck should require superuser privilege"),
> bq. I agree that it makes sense to make fsck do permission checking for the
> nodes that it traverses. If a user does a fsck on files/directories that
> he/she has access to (using permissions) then that invocation of fsck should
> be allowed. Since "/" is usually owned by super-user, only super-user should
> be allowed to run fsck on "/".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
