singlelat.blogg.se

• BETTER SNAP TOOL MAC MOJAVE MAC OS

I was able to test only a little, but found something interesting. Given that ACLs live at the filesystem level and have been in OS X for many years now, it's fairly improbably that they're "broken" in Mojave. Sudo chmod +a "user:jpublic allow readsecurity,readattr,readextattr,list,search,read,execute,writeattr,writeextattr,delete,add_file,add_subdirectory,delete_child,write,append,file_inherit,directory_inherit" DirectoryNameToApplyACLTo Sudo chmod -R +a "group:yourgroupname allow readsecurity,readattr,readextattr,list,search,read,execute,writeattr,writeextattr,delete,add_file,add_subdirectory,delete_child,write,append,file_inherit,directory_inherit" DirectoryNameToApplyACLTo That syntax is wrong in terms of required items/arguments/parameters, it should throw an error as it's missing a required element of user or group: It's very sad that we can't just pay more to get the functionality we used to get at the price we used to pay. A separate issue is how disrespectful Apple has been in the treatment of its server customers. Not available in the Server.app as described. Apple's current server documentation suggesting the creation of a group folder is hilarious, as they have ripped out that functionality. The ACLs look correct when doing an ls -le on the directory.Īgain, this seems to work ok in High Sierra. This is after setting up the Shared Folder, and I have also tried setting the POSIX permissions recursively for the group to be able to read, write, and execute. Sudo chmod -R +ai "staff allow list,add_file,search,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeextattr,readsecurity,file_inherit,directory_inherit" I have set ACLs recursively using both the group name and the usernames in question. Then that new file is not able to be deleted except by the creator, until an unmount has occurred. Reapplying ACLs seems to fix the issue, but only until another file is created. Only unmounting the share on the computer that created the file seems to allow the file to be deleted. This is even when the computer that created the file is not in the folder in any way (not in terminal, nor in Finder). It says the file cannot be deleted because it is in use.

If I create a folder, then a subfolder inside of that, within a share, then try to delete it from another computer, it throws an error.

A folder created on a share can be deleted from another computer. However, I am now configuring a new Mac Mini Server, which ships with Mojave. They do seem to work on High Sierra, and I have a machine sharing files which is running High Sierra.

BETTER SNAP TOOL MAC MOJAVE MAC OS

Have read through multiple questions on the topic of ACL inheritance on Mac OS X, but unfortunately, none seem to be effective in solving this issue in Mojave.