On Jun 10, 2009, at 1:18 AM, Robert Purves wrote:

>
> Steve wrote:
>
>> If you share a folder on a server and that folder has permissions  
>> so that anyone can read/write to the folder, why is it that new  
>> files created in the folder only have write permissions for that  
>> user?
>> Is this the correct operation of the OS?  It seems that something  
>> may have changed in 10.5.7 with regard to permissions.
>> Don't files created take on the attributes of the folder it is in?
>> Any help would be appreciated.
>
>
> How are you creating these files? If programatically, does your app  
> call fn umask( 0 )?
>
> umask( 0 ) sets read/write permissions for owner, group, others.
> For details, in Terminal.app type:
> man 2 umask
>
> Robert P.

I've been wondering...

Is there some protocol or rules one is supposed to use when using  
umask? Because I've had crashes using it before and after saving  
files (set permisions, restore to prior after, etc)

Can you set it once, at app start and not worry about it again until  
resetting at end? So all your files work to be opened by all users?

Robert


PID:    483
Thread: 0

Exception:  EXC_BAD_INSTRUCTION (0x0002)
Code[0]:    0x00000002
Code[1]:    0xa07bc718


Thread 0 Crashed:
0   <<00000000>> 	0xa07bc718 kCFNotificationAnyName + 8
1                                  	0x0045ca48 umask + 40
2                                  	0x0045cd38 PresetPerms + 36
3                                  	0x00466718 NavDoSaveCustom + 1828
4                                  	0x00757e74 FileMenu + 932
5   <<00000000>> 	0x00384980 0 + 3688832