That's all helpful, thanks. These are not directories and I can see why they wouldn't want these files to be executable. ES On Feb 10, 2010, at 6:19pm, Mark J. Reed wrote: > Make that a=rw to set the permissions exactly ( which the numerical > form always does ). The + version adds rw and leaves x as it found > it... But be careful. Directories have to be executable or you can't > access their contents. > > On Wednesday, February 10, 2010, Mark J. Reed <[log in to unmask]> wrote: >> 6 is read+write. 7 is read+write+execute. You could also use the >> symbolic form "a+rw" (all plus read write). >> >> The numbers are user, group, other, in that order, where each digit is >> the sum of the granted permissions: 4 for read, 2 for write, and 1 for >> execute. >> >> On Wednesday, February 10, 2010, Stockly, Ed <[log in to unmask]> wrote: >>> Thanks Shane, that did the trick. >>> >>> The UNIX guys getting the files said they preferred 666 to 777, and I'm not >>> sure what the difference is, but it was easy enough to fix. >>> >>> >>> ES >>> >>> set procfile to quoted form of POSIX path of procfile >>> set permisionsShell to "chmod 666 " & procfile >>> do shell script permisionsShell >>> >>> >>> >>> On 2/10/10 3:38 PM, "Shane Stanley" wrote: >>> >>>> On 11/2/10 10:24 AM, "Ed Stockly" <[log in to unmask]> wrote: >>>> >>>>> Is there a do shell script that can do this? >>>> >>>> Probably: >>>> >>>> do shell script "chmod 777 " & quoted form of POSIX path of ... >>>> >>>> For directories or packages where you want the whole contents changed: >>>> >>>> do shell script "chmod -R 777 " & quoted form of POSIX path of ... >>>> >>> >> >> -- >> Mark J. Reed <[log in to unmask]> >> > > -- > Mark J. Reed <[log in to unmask]>