I pretty sure sticky bit isn't supported in PVFS2 generically, only implemented at the root "/" directory, and permission checking for the sticky bit implemented on the client side VFS layer. Should the sticky bit on "/" level be considered in the mix for permissions for pvfs2 command line utilities, namely pvfs2-rm? For the example below, rmdir commands with userB through the VFS layer fail for "rmdir /mnt/datagrid0002/client03", but issuing a "pvfs2-rm /mnt/datagrid0002/client03" command with userB, the permissions pass, due to the write permissions for 'others' on the parent directory, and client03 is deleted. Removing the write access for others and both VFS and pvfs2-rm behave similarly, although the error message from pvfs2-rm seems a bit generic (PVFS_sys_remove: No such file or directory (error class: 0)).
ls -l /mnt drwxrwxrwt 1 root root 4096 Mar 11 11:47 datagrid0002 ls -la /mnt/datagrid0002/ drwxrwxrwt 1 root root 4096 Mar 11 11:47 . drwxr-xr-x 1 userA userA 4096 Mar 11 11:47 client03 Thanks, David
_______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
