Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I often try to find files with following syntax:

find . -name "filetofind"

However it usually results as many rows or error reporting (Permission denied) about folders where permission is denied. Is there any other way to avoid this spam than using sudo or advanced grepping from error-output?

share|improve this question
up vote 15 down vote accepted


find . -name "filetofind" 2>/dev/null

This will redirect stderr output stream, which is used to report all errors, including "Access denied" one, to null device.

share|improve this answer
Thanks, works like a charm :) I suppose there is no easy way to make it default option without creating an alias doing the same. – user40167 Aug 24 '10 at 11:01
No, this is by design of the shell. – whitequark Aug 24 '10 at 11:10

If you want to see other errors and you don't have files named "permission denied" then this will work "better".

find . -name "filetofind" 2>&1 | grep -v 'permission denied' 

Redirecting the output to grep with the inversion option.

share|improve this answer

You can also use the -perm and -prune predicates to avoid descending into unreadable directories (see also How do I remove "permission denied" printout statements from the find program? - Unix & Linux Stack Exchange):

find . -type d ! -perm -g+r,u+r,o+r -prune -o -name "filetofind" -print
share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .