"No such file or directory" within /proc ?
Hi List, while doing a "du" in /proc, I get the following error msg: du: `./2220/fd/4': No such file or directory not quite sure, but doesnt "fd" mean a file descriptor? could it be an installed rootkit causing that error msg? Greeets Chr. Burri .-. /v\ L I N U X // \\ >I know KungFu!!< /( )\ ^^-^^
Hi christian.burri! On Thu, 04 Oct 2001, christian.burri@synecta.ch wrote:
Hi List,
while doing a "du" in /proc, I get the following error msg:
du: `./2220/fd/4': No such file or directory
fd is a directory with opened file descriptors of the process I saw the error once in a while when the fd is probably exactly of the process trying to access proc (in this case du). -- teodor
teo@gecadsoftware.com wrote:
Hi christian.burri! On Thu, 04 Oct 2001, christian.burri@synecta.ch wrote:
Hi List,
while doing a "du" in /proc, I get the following error msg:
du: `./2220/fd/4': No such file or directory
fd is a directory with opened file descriptors of the process I saw the error once in a while when the fd is probably exactly of the process trying to access proc (in this case du).
-- teodor
Indeed, Teodor has the answer. One can see from the following:
cnr2:/proc # du
while doing a "du" in /proc, I get the following error msg:
du: `./2220/fd/4': No such file or directory
not quite sure, but doesnt "fd" mean a file descriptor? could it be an installed rootkit causing that error msg?
This is usually caused by defunct cron processes, in which case it's nothing to worry about. 2220is the process number check what process that is. If it is a cron process, check your crontab. Cheers. Yuri.
Hi List,
while doing a "du" in /proc, I get the following error msg:
du: `./2220/fd/4': No such file or directory
not quite sure, but doesnt "fd" mean a file descriptor? could it be an installed rootkit causing that error msg?
/proc/<pid>/fd is a directory with symlinks to the currently open files of the process with pid <pid>. In your case, the du binariy seemed to occupy pid 2220, and it stumbled over its own fd-symlinks. This is a race condition, between a getdents(2) and a following lstat(2) system call inside of du (the link is gone after the close(2) on the directory filedescriptor). It should not be worth the effort since du doesn't make sense in /proc (there is no disk space allocated there, the files and directories are there for us to see them only). Use "du -kx" to stay in the same filesystem.
Greeets Chr. Burri
Regards,
Roman.
--
- -
| Roman Drahtmüller
participants (5)
-
christian.burri＠synecta.ch -
Richard Witt -
Roman Drahtmueller -
teo＠gecadsoftware.com -
Yuri Robbers