Quote:
Originally Posted by
Srivathsava
But if I am in a/b directory and searching for that file with that command and if any sub folders of b,c or d doesn't have read permissions, its stopped searching there.
That's the entire point of the security model. If you do not have read permission you are not allowed to read. You either need to run
find as a different user, one that has read permission, or the file hierarchy's ownership and/or permissions need to be modified.
If I recall correctly, for a find traversal you'll need read permissions for every directory that is visited, and execute (search) permissions for every path component, even if it's upstream and not visited. So if you start your search at directory "d" with hopes of reaching "f", whose path is /a/b/c/d/e/f/, you will need execute permission on every directory from the root to "f", but you'll only need read permissions for "d", "e", and "f".
With
cd, you can "jump" to a directory, but only if you know its location and have execute permission on every directory above it. If you lack that permission on even just one of its ancestors, you won't be able to make it the current working directory. Once in that directory, you'll still need read permission to list its contents and write permission to create/delete files.
Regards,
Alister