Date: Mon, 10 Sep 2007 22:58:53 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: chmod / files and directories Message-ID: <20070910225853.6b7321ec@gumby.homeunix.com.> In-Reply-To: <p06240802c30b513d7a35@[128.113.24.47]> References: <94136a2c0709100856q768b101as96e1e6d16312d374@mail.gmail.com> <20070910160607.GA20159@catflap.slightlystrange.org> <20070910161006.GB20159@catflap.slightlystrange.org> <A2DB3A06-0AC3-4975-AAD0-75638560AC76@gmail.com> <20070910173609.GC20159@catflap.slightlystrange.org> <46E58105.4000200@ridecharge.com> <p06240802c30b513d7a35@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10 Sep 2007 15:59:31 -0400
Garance A Drosihn <drosih@rpi.edu> wrote:
> At 1:38 PM -0400 9/10/07, Philip M. Gollucci wrote:
> >Daniel Bye wrote:
> >> On Mon, Sep 10, 2007 at 10:01:35PM +0530, Shantanoo Mahajan wrote:
> > >> # find /usr/local/www/data/wp -type f -exec chmod 644 '{}' \;
> >>> # find /usr/local/www/data/wp -type d -exec chmod 755 '{}' \;
> >>>
> >>> To be on safer side. :)
> >>
> >> Oh? Safer how? I've never come across that idiom before.
> >
> >If imange the file or directory name has spaces, (){}-, etc.. in
> >it or even \.
>
> This is not necessary with -exec in the 'find' command, and the
> single-quotes wouldn't have any effect. The {} is a parameter
> which is seen by the find command itself. If you add single-quotes
> around the {}, those quotes are stripped off by the *shell* before
> handing the parameter off to the 'find' command.
And special characters in the filenames aren't a problem since "find"
passes the arguments directly to chmod as an array of null-terminated
strings, so they don't get interpreted by the shell.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070910225853.6b7321ec>