Greg,
The office has some employees (I will call them the "Admins" group) who need access to a shared volume /folder. But other employees (I will call them the "Others" group) are not allowed to see the shared item when they choose "Connect to Server" and they certainly are not allowed to browse or alter the contents. In 10.6 Server, these groups worked fine -- Admins had read/write access to all files and folders that were designated specifically for their eyes only. Most importantly, Admins could open and alter files, regardless of the original file owner. And the Others had zero access.
Upon upgrading to 10.9 Server, these access permissions went to hell. Now, Admins cannot open each other's files; they are alerted the file is in use and/or locked and/or they have no permission to save the altered file with the same name in the same location.
For me to choose "Ignore Ownership" on a volume or a folder on the Server will not be an option, due to the conditions described above.
thanks anyway!
The office has some employees (I will call them the "Admins" group) who need access to a shared volume /folder. But other employees (I will call them the "Others" group) are not allowed to see the shared item when they choose "Connect to Server" and they certainly are not allowed to browse or alter the contents. In 10.6 Server, these groups worked fine -- Admins had read/write access to all files and folders that were designated specifically for their eyes only. Most importantly, Admins could open and alter files, regardless of the original file owner. And the Others had zero access.
Upon upgrading to 10.9 Server, these access permissions went to hell. Now, Admins cannot open each other's files; they are alerted the file is in use and/or locked and/or they have no permission to save the altered file with the same name in the same location.
For me to choose "Ignore Ownership" on a volume or a folder on the Server will not be an option, due to the conditions described above.
thanks anyway!