SUMMARY: Strange output from FIND in cron

From: Alan G. Arndt (
Date: Fri Aug 23 1991 - 17:16:38 CDT

Well the problem I reported:
        Your "cron" job

        find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune

        produced the following output:

        find: cannot stat /home/clip-art: No such file or directory
        find: cannot stat /home/tcp: No such file or directory

basically disappeared as mysteriously as it appeared. I got quite a few
comments from people mostly talking about the automounter. As we don't
use the automounter that isn't the problem. Several others mentioned
permission problems, yet I can find nothing wrong with the files in that
area. The only other comment was about the possible system load when this
process was running. As it turns out Our news feed was down for several
days and the load from expire eventually tapered off, that is when I stopped
getting the messages. I have since moved the expire farther in time from the
find job and we will see what happens over the next week. This doesn't seem
to be the entire solution though as I did run this job by hand on a totaly
idle system and got the same output. And the expire is running on a
different drive from the find errors. The net result is that the problem
has disappeared but I am not really sure why or if it will come back.

Thank you all very much for your comments.
Alan Arndt

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:19 CDT