default execute permission
Hello, Im using SLES 8. My system umask is set to 022. When a file is created the permissions are set to -rw-r--r--. How can I make it so that any new file created is executable by the owner? Thanks, Ryan
The Monday 2005-01-10 at 16:27 -0600, Ryan McCain wrote:
Im using SLES 8. My system umask is set to 022. When a file is created the permissions are set to -rw-r--r--. How can I make it so that any new file created is executable by the owner?
_any_ new file executable? I would think that to be a security risk... umask [-p] [-S] [mode] The user file-creation mask is set to mode. If mode begins with a digit, it is interpreted as an octal number; otherwise it is interpreted as a symbolic mode mask similar to that accepted by chmod(1). If mode is omitted, the current value of the mask is printed. The -S option causes the mask to be printed in sym bolic form; the default output is an octal number. If the -p option is supplied, and mode is omitted, the output is in a form that may be reused as input. The return status is 0 if the mode was successfully changed or if no mode argument was supplied, and false otherwise. The system default is set in /etc/profile: umask 022 -- Cheers, Carlos Robinson
Ryan, On Monday 10 January 2005 14:27, Ryan McCain wrote:
Hello,
Im using SLES 8. My system umask is set to 022. When a file is created the permissions are set to -rw-r--r--. How can I make it so that any new file created is executable by the owner?
Nothing you can do will accomplish that. There is the umask mechanism (as Carlos pointed out), but it operates by _removing_ permission bits when files are created. The program that creates the file will use permissions like 0666 for plain files and 0777 for executable files and directories. Thus, you'll find that linker ("ld") output is executable (with umask bits turned off, of course) but that ordinary text files created by a text editor will not. If such files are scripts, then you'll have to add the execute bits yourself: % chmod +x scriptFile There's basically nothing you can do to work around this mechanism, since it's a matter of both the creating application and the kernel-imposed umask mechanism. Apart from the umask setting itself, none of this is within your control.
Thanks, Ryan
Randall Schulz
participants (3)
-
Carlos E. R.
-
Randall R Schulz
-
Ryan McCain