This is pretty standard for POSIX permissions. Even though a containing folder can have the appropriate permissions, the owner of the file is still the one who created it. In order to properly ensure your cohorts can read and write to every file in a share, you need to create a user with the same user name and password and then apply read write permissions for that user to the shared folder in the sharing tab of the system settings. It’s actually not that different than Windows peer to peer permissions.
The proper way to do this is to put the shared data in the Public folder. This will get you around all the sandboxing issues you may encounter accessing folders in another users profile. Bob S On Jan 17, 2015, at 20:19 , Dr. Hawkins <doch...@gmail.com<mailto:doch...@gmail.com>> wrote: Also, OSX can be downright schizophrenic about the permissions, with conflicting ways of doig things. My macs got added to unix networks, with preexisting groups & users. One mac worked fine on the network, but after a couple of years, I still end up with files created by my assistant on my machine being unwritable by me, and vice versa. -- Dr. Richard E. Hawkins, Esq. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
