hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Macdonald (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4368) Superuser privileges required to do "df"
Date Thu, 04 Dec 2008 18:02:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653388#action_12653388
] 

Craig Macdonald commented on HADOOP-4368:
-----------------------------------------

bq. Does that mean that anybody will be able to connect to HDFS as a superuser via fuse?

No. Brian's patch allows the statfs call (as represented by the df command) to work correctly,
by calling  the appropriate libhdfs methods as superuser, before dropping the connection.

The moving of the appropriate API from DistributedFileSystem to FileSystem is indeed fairly
straightforward. I guess I was raising the question as to whether that would be permitted
for 0.19.1, as I obviously view the current proposed patch as an interim fix.

> Superuser privileges required to do "df"
> ----------------------------------------
>
>                 Key: HADOOP-4368
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4368
>             Project: Hadoop Core
>          Issue Type: Wish
>          Components: contrib/fuse-dfs, dfs
>    Affects Versions: 0.18.1
>            Reporter: Brian Bockelman
>            Priority: Minor
>         Attachments: fuse_statfs.patch, fuse_statfs_trunk.patch
>
>   Original Estimate: 0.17h
>  Remaining Estimate: 0.17h
>
> super user privileges are required in DFS in order to get the file system statistics
(FSNamesystem.java, getStats method).  This means that when HDFS is mounted via fuse-dfs as
a non-root user, "df" is going to return 16exabytes total and 0 free instead of the correct
amount.
> As far as I can tell, there's no need to require super user privileges to see the file
system size (and historically in Unix, this is not required).
> To fix this, simply comment out the privilege check in the getStats method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message