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-4106) add time, permission and user attribute support to fuse-dfs
Date Fri, 12 Sep 2008 20:39:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630678#action_12630678

Craig Macdonald commented on HADOOP-4106:


Is it for connectAsUser or chown that you are having the issue?

See my attachment for HADOOP-3536. This worked OK for me on Linux, and MacOSX IIRC.

2. Also, I was thinking about the {{gid_t uid = context->gid;}}

Surely this only gives the default group of the user? How would this work in my setting, where
my default group represents my status, while most files are protected on a groups which are
assigned on a project level basis? 

In the RPC mechanism used by NFS, the following struct is used to pass authentication information
from client to server (source: https://trac.eecs.iu-bremen.de/projects/scotty/browser/branches/tubs/compat/rpc/auth_unix.h?rev=885):
struct authunix_parms {
        u_long   aup_time;
        char    *aup_machname;
        int      aup_uid;
        int      aup_gid;
        u_int    aup_len;
        int     *aup_gids;

The point s that a process accessing a file in the NFS client has a uid and a gid. However,
the NFS client supplements the gid with the other gids that the user belongs to. We should
do likewise.

> add time, permission and user attribute support to fuse-dfs
> -----------------------------------------------------------
>                 Key: HADOOP-4106
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4106
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: contrib/fuse-dfs
>            Reporter: Pete Wyckoff
>            Assignee: Pete Wyckoff
>             Fix For: 0.19.0
>         Attachments: HADOOP-4106.txt, HADOOP-4106.txt
> add:
> dfs_chown
> dfs_utime
> dfs_chmod
> Change open to have its own FS on writes (should we do this on reads too??) and use it
for writes and disconnect when closing the file
> Chane mkdir to open the FS itself and then close it
> also added comments for dfs_access (which needs FileSystem support/libhdfs support) and
I added the dfs_symlink and truncate since these 3 are the only 3 things left as far as functionality.

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

View raw message