Hi Everyone,
this seems to be an issue for us also, since we upgraded to a new server running OS X.4 and moved all of our files over from our old server. We began seeing behavior where users would create files and folders which could not be changed by anyone else, which I presume is a result of the umask setting. Our first teamwork file in AC 11 kept giving errors "can not write teamwork notes" which I fixed by changing the permissions of all the project files to Read/Write by everyone.
Since our network guru has moved across the pond to Switzerland, and our local tech support seems to be bleeding competent people, perhaps users here can help. Previously in server osx.3 when we made files I believe the owner was admin (the admin user of the server) and everyone could read and write. now, sometimes, the owner is whichever user made the file, and sometimes, but not always, only the owner can write to the file. Shouldn't files inherit permissions from the parent folder or does that only occur when one particularly tells it to do that? why might some files be owned by admin and others be owned by individual users?
besides changing the umask defaults for all users on the whole server, is there a way to change the setting for each user individually? We have a very small network.
we are also having problems with permissions on older AC9 projects which may be related to this.
Thanks!
Katie Bertsche
OSx server X.4.9
Dualcore Intel Macs X.4.9
AC11
AC9