Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
/proc/ is a virtual filesystem that reports things about the running kernel.
The directory /proc/pid contains information on a running process. In this case, the process ID (PID) of the process is 6827.
The reason that you are seeing this message is that find gets the directory contents of /proc/, as part of its search through the filesystem, and then tries to access each directory in turn.
Unfortunately, the pid process ends in between find reading the directory contents, and actually entering the pid directory. So the attempt to change to that directory fails, hence the error message.
It probably has to do with two things: user ID (versus root ID) and user directory/file permissions (versus root permissions). When running such a broad search as user (find / searches the entire filesystem), you should get a lot of 'permission denied' returns for the directories user is denied permission to look into. The process in question may be associated with the ID of the individual running find. It may exist for root, but not for user.
Try opening a term and su to root, then run the same find again. See if the same (or similar) line shows up again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.