Newsroom Update
Beginning in May, a special Today at Apple series titled “Made for Business” will offer small business owners and entrepreneurs free opportunities to learn how Apple products and services can support their growth and success. Learn more >
Beginning in May, a special Today at Apple series titled “Made for Business” will offer small business owners and entrepreneurs free opportunities to learn how Apple products and services can support their growth and success. Learn more >
I have a system wherein files are automatically pulled from an FTP, and are placed in a specific folder on our Mac Server running 10.5. The issue is that the files when pulled have their permission as "No access" to user everyone. Is it possible to create a hot folder that automatically changes everything put into as "Read Write" to user everyone?
Thanks!
R~
Mac OS X (10.5.8)
Hi
Yes. Provide an overriding ACL for a specific user or users or group or group of groups. Define Read/Write access and propagate the permission.
The "No Access" permission you're seeing is set using the default POSIX Permissions Model. The ACL Model supercedes and can also combine, in some situations depending on what you want, with the POSIX Model.
HTH?
Tony
Hi there-
Thanks for the assist. The issue we are having is they can access them after we propogate permissions, but the folder is receiving new files constantly. Therefore, we have to stop production, propogate permissions, which doesn't really help us.
What I am hoping to achieve is a folder that no matter what you put in it, it has automatically sets file permissions read/write to all users. Is this possible?
Thanks!
R~
Hi
Are you propagating POSIX permissions or ACL Permissions? if you're only propagating POSIX permissions it won't work and you'll soon end up back to only creator/owners of files and/or folders having read/write access and everyone else read only.
If you are propagating ACLs and you're having to do this regularly then there's something wrong elsewhere? It's a good idea not to share the volume but rather a folder within the volume. If ACL permissions are not propating properly or they are not sticking after propagation then un-share the share, rename the folder, create another folder named the same as it was before you renamed it and transfer the contents of the olf folder to the new onr. Re-share that new folder, add users or groups to the ACL Window, define appropriate permissions and re-propagate. This should now work without any further propagation.
If it's still not working I would start troubleshooting possible drive/directory issues. Use something like DiskWarrior or even Disk Utility. If the share(s) are on a non-boot volume then un-share the shares, do what you have to and re-share them again. Re-propagate afterwards. I can assure you this does work and works well but if there are underlying issues with either the Server Configuration (possible) or the drive/directory structure (more likeley) of the volume where the shares are stored you will see problems.
HTH?
Tony
Actually, we've discovered that the sync program we are using is causing the issues. We've switched that, and the problem went away. Thank you, though, because I learned a lot here!
Hot Folder to Force File Permissions?
