So if you have something like this:

drwxr—– somedir
-rwxr—– somefile

you’ll end up with:
drwx–x–x somedir
-rwx–x–x somefile

instead of the wanted:
drwx–x–x somedir
-rwx—— somefile

It depends if this is desirable or not, but you should point this out in your post.

Debashish,
For each result of find, chmod {} is executed. All occurences of {} are replaced by the individual filenames found. ; is prefixed with a backslash to prevent the shell from interpreting it. ; moves to the next command. It is often used in a series of commands in scripts… see PHP or javascript. ; is also often used in a simple command line script to perform a number of commands in sequence.

See http://linux.die.net/man/1/find and look for -exec command ;

It basically does the recursive chmod but also provides a bit of flexibility for command line options (sets directory and/or file permissions, or exclude both it automatically resets everything to 755-644). It also checks for a few error scenarios.

Check it out:
http://bigfloppydonkeydisk.blogspot.com.au/2012/09/recursively-chmod-only-files-or.html

Hope it helps!

If ls -l or ls -al shows d????????? then you probably should try to chmod again to 644 using the method described above, the first chmod command in this post.