On Jul 27, 2010, at 12:26 PM, Dan Shoop wrote: > > On Jul 27, 2010, at 12:13 PM, Chris Murphy wrote: > >> >> On Jul 27, 2010, at 9:32 AM, Dan Shoop wrote: >>> >>> The latter is not a supported operation. Yes, I know that sounds crazy but >>> that's not a workflow Adobe approves of with their products Instead save >>> locally, then copy. Directly saving files in Adobe products to fileshares >>> has never been supported by Adobe. >> >> Understood but it has worked flawlessly from InDesign for a year with POSIX >> permissions. Upon changing to ACLs, we get a permissions error from >> InDesign. Today we removed the ACLs, and went back to conventional >> permissions and now InDesign can write directly into these drop folders. > > Which only indicates that you did not properly capture the required set of > ACEs. Anything you can do with ownerships and permissions you can achieve > better with ACLs.
Seems like a reasonable explanation. Admins on the other end are telling me that during the test phase the ACLs were working correctly for all users and all drop folders. And then inexplicably a week into deployment users started getting the permissions error from InDesign. And this approximately coincides with the XServe announcing a SMART failure prediction for one of the mirrored drives. So for all I know, iffy drives are corrupting themselves and it's just coincidentally making ACLs look like the problem. Chris Murphy_______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
