hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-9155) FsPermission should have different default value, 777 for directory and 666 for file
Date Wed, 19 Dec 2012 06:13:14 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-9155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Colin Patrick McCabe updated HADOOP-9155:
-----------------------------------------

    Description: 
The default permission for {{FileSystem#create}} is the same default as for {{FileSystem#mkdirs}},
namely {{0777}}. It would make more sense for the default to be {{0666}} for files and {{0777}}
for directories.  The current default leads to a lot of files being created with the executable
bit that really should not be.  One example is anything created with FsShell's copyToLocal.

For reference, {{fopen}} creates files with a mode of {{0666}} (minus whatever bits are set
in the umask; usually {{0022}}.  This seems to be the standard behavior and we should follow
it.  This is also a regression since branch-1.

  was:
Currently umask works differently as linux convention, which is:
The default umask 0002 is used for regular users. 
The default umask for the root user is 0022.
For directories, the base permissions are 0777 and for files 0666.

    
> FsPermission should have different default value, 777 for directory and 666 for file
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9155
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9155
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Binglin Chang
>            Priority: Minor
>
> The default permission for {{FileSystem#create}} is the same default as for {{FileSystem#mkdirs}},
namely {{0777}}. It would make more sense for the default to be {{0666}} for files and {{0777}}
for directories.  The current default leads to a lot of files being created with the executable
bit that really should not be.  One example is anything created with FsShell's copyToLocal.
> For reference, {{fopen}} creates files with a mode of {{0666}} (minus whatever bits are
set in the umask; usually {{0022}}.  This seems to be the standard behavior and we should
follow it.  This is also a regression since branch-1.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message