On Jul 27, 2010, at 1:44 PM, LuKreme wrote: > On 26-Jul-2010, at 22:34, Chris Murphy wrote: >> >> 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. But I don't know anything about how >> ACLs are implemented, and if and how aware of ACLs an application would need >> to be or if there is some other interaction that could be going on, maybe >> even with AFP as the intermediary. > > So this happens only when InDesign writes the file? > > Is this a drop box type folder (write access, no read)? > > I know drop boxes are a problem on Windows machines, so it would not at all > surprise me if Adobe didn't understand them. Or it's just adobe being stupid > and doing something to actively not support ACLs.
There is no such "thing" as a 'dropbox' per se. It's just a directory, like any other. The issue here is that InDesign needs access to more than what is readily apparent. It most likely creates temp files, and sometimes apps like to create these in strange places, like the volume root, and most likely performs other operations other than just opening a single file for write. You can use dtrace to capture the actual behavior and then you'll know much, much more about what it's doing and about why everyone's presumption - that it merely opens a single file for write, maybe fiddling with the containing directory - is inadequate to explain the situation. -d ------------------------------------------------------------------------ Dan Shoop Computer Scientist [email protected] GoogleVoice: 1-646-402-5293 aim: iWiring twitter: @colonelmode _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
