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. > >> Now, with ACL based shared folders, InDesign reports "Cannot save to the >> file "blah.pdf". You may not have permission or the file may be in use." And >> then it proceeds to write out a zero K PDF. I'm not sure that it's ACL >> related, it might be something else. > > It's not related to the ACLs you have, but to what directories and files > Adobe products try to access when saving files and their expectations for > writing to the volume, temp files, and files it use for all it's > relationships with other Adobe products. It seems the expectations for at least InDesign is different between POSIX permissions and ACLs. The Finder behavior is consistent with either method, but InDesign is not. Chris Murphy_______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
