Different method of setting permisions that apply to newly created files between legacy and OS6?
Hi all,
Am I correct in assuming that on OS6 the permissions for newly created files and directories are handled differently from the way there were on legacy (4.2 OS)? By this I mean when using the GUI to define what permissions should apply to new files / folders created under a given share.
Previously, when setting the permissions that should apply to newly created files / folders this was achieved by using the create mask attributes within Samba (smb.conf). However, on OS6 this now seems to be achieved using Linux ACL’s.
I discovered this during the migration of data from a legacy system to a new OS6 based system. I’d used rsync which preserves the permissions on content. This then caused some issues since the ACL’s had effectively been overwritten or changed.
In the final analysis I was able to resolve this (once I discovered what had happened) by resetting the permissions on the shares from the GUI.
Re: Different method of setting permisions that apply to newly created files between legacy and OS6?
Thanks...
It can and did cause issues when using rsync to move files over from my old legacy system... Essentially the mask applied by the ACL is removed and that then means that new files are not created with the intended permissions. Once I found out what was happening, I resolved the issue by resetting the permissions. However, any future rsync transfers would cause the permissions to revert to a broken state.
Fortunately for me this is a migration activity so not a problem.
Re: Different method of setting permisions that apply to newly created files between legacy and OS6?
OS6 has a number of improvements over RAIDiator-x86 4.2. The UIDs and GIDs may be different for users as well so copying the data over and resetting the ownership/permissions then configuring it how you would like is the way to go.
