Server Fault is a question and answer site for system and network administrators. 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
# find / -user root -perm -4000 -print
find: /proc/21944/task/21944/fd/4: No such file or directory
find: /proc/21944/fd/4: No such file or directory
share|improve this question
Yes. What of it? – Ignacio Vazquez-Abrams Jan 20 '11 at 0:35
up vote 3 down vote accepted

Yes, that's completely normal. The /proc virtual filesystem provides an interface to the process and memory information on a system. This allows tools like top(1) to use normal filesystem calls to examine processes and memory instead of doing non-portable mucking about in the system memory. Information in this filesystem changes constantly as the state of the system changes. In your example, file descriptor 4 for process 21944 was closed after the find command found it in the directory but before it could read it.

Since /proc is not a real filesystem, you usually want to avoid it in any traversals of your filesystem. Here's some more info on using /proc in linux.

share|improve this answer
You can use something like find / -path /proc -prune -or -user root -perm -4000 -print. – jon Jan 20 '11 at 1:52

If you're concerned about the "No such file or directory" messages, in this case it means that those file descriptors for those processes were closed during the operation of the find command or the processes exited (which also means the file descriptors were closed). You can also get that message for broken symlinks.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.