Setting a umask to 006 is almost certainly not what you want. Not a knock,
but I just wanted to explain it so that the issue is clear.

Technically, yes you are correct that files are created with a mask of
666, unless the files are executable. In that case they would come out
with a mask of 777. So, if you set your umask to 006 and then you go to
link a file, then that file would have a mask of 771 (rwxrwx--x) which is
probably not what you want. This is why common values for each of the
digits of a umask are either 2 to prevent writing, or 7 to prevent all
access.

-- 
-Time flies like the wind. Fruit flies like a banana. [EMAIL PROTECTED]
-Stranger things have happened but none stranger than this. Steven W. Orr-
Does your driver's license say Organ Donor?Black holes are where God \
-------divided by zero. Listen to me! We are all individuals!---------


On Sun, 20 Aug 2000, rpjday wrote:

=>On Sun, 20 Aug 2000, Gary Nielson wrote:
=>
=>> Hi,
=>> 
=>> I need to make a system-wide change so that every user when creating a
=>> file will have it set to rw-rw----. So the umask setting would be 007. I
=>> understand that by changing the setting in /etc/profile, it will go into
=>> effect system wide for all current and new users. Is that right? Does this
=>> have the same effect as adding "umask 007" to each user's .bashrc file. Or
=>> if changing it for an individual user, should it be the .bash_profile
=>> file? Finally, when changing /etc/profile, I do not understand what the
=>> following means:
=>> 
=>> if [ `id -gn` = `id -un` -a `id -u` -gt 14 ]; then
=>>         umask 002
=>> else
=>>         umask 022
=>> fi
=>> 
=>> Since all files are now created on my system with a umask level of 002, I
=>> am *assuming* that I would make the change to 002 in the above if/else
=>> statement, but I am not sure what the above does, so I don't want to
=>> change it without first understanding it.
=>
=>1) setting a umask in /etc/profile doesn't prevent users from
=>  setting it to some other value in their own .bash_profile
=>
=>2) technically, files are created with a starting permission of
=>  rw-rw-rw-, or 666.  so your umask need only take out the final
=>  two permissions, as in "umask 006".



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to