Mailinglist Archive: opensuse (3397 mails)

["Hylton Conacher (ZR1HPC)" <hylton@xxxxxxxxxxxx>]

Randall R Schulz wrote:
> Erik,
> ........(snippee)
>
> I've done this before on this list, but here goes...
>
> Every time a program creates a file, it specifies a set of permission 
> bits. If the program is a plain file, the program will usually 
> (_usually_, not always) specify 0666 (read+write for owner, group and 
> others). If the program is creating a directory or an executable file, 
> it will usually use 0777 (read+write+execute for owner, group and 
> others).
Thank you Eril and Randall. Although I knew that the umask was related 
to file security, I did not know how it was applied. So when the file is 
created the umask decreases the privileges and then only the owner, in 
SuSE, can change the permissions, but the umask will not affect the new 
permissions ie a file is created (0666), umask(022) intervenes and makes 
it (0644). If the user now changes the permissions to 0666 the umask 
does not reset the permissions.

[snip]

I hope it helped Erik as it certainly did help me.
--
========================================================================
Hylton Conacher - Linux user # 229959 at http://counter.li.org
Currently using SuSE 9.0 Professional with KDE 3.1
========================================================================