When running tmpwatch with --fuser on a sufficiently loaded system, it's common to get errors like this on stderr: # tmpwatch --mtime --fuser --quiet 504 /usr/portage/distfiles Cannot stat file /proc/10661/fd/542: No such file or directory Cannot stat file /proc/10661/fd/549: No such file or directory Cannot stat file /proc/10661/fd/587: No such file or directory Cannot stat file /proc/10661/fd/593: No such file or directory We can't send stderr to /dev/null since this would mask legitimate errors from tmpwatch. The best solution would be to ignore this race condition in tmpwatch.
Which version of tmpwatch is this?
$ equery l tmpwatch * Searching for tmpwatch ... [IP-] [ ] app-admin/tmpwatch-2.10.1:0 FWIW, I've seen this problem for quite some time but only recently realized it was due to fuser.
(In reply to comment #2) > $ equery l tmpwatch > * Searching for tmpwatch ... > [IP-] [ ] app-admin/tmpwatch-2.10.1:0 Please try 2.10.3.
Upgrading to 2.10.3 doesn't seem to help. There is still a race condition caused by tmpwatch trying to look at processes that no longer exist. For example, tmpwatch produces errors like this: Cannot stat file /proc/4892/fd/51: No such file or directory Cannot stat file /proc/8860/fd/7: No such file or directory Cannot stat file /proc/5474/fd/7: No such file or directory This can be reproduced by running tmpwatch --mtime --fuser --quiet 504 /usr/portage/distfiles
Try with 2.11-r1
