> Every once in a while, my computer hard-drive makes lot of noise and the
> whole computer seems unresponsive. When that happens, I also find this
> command running and making all the ruckus:
> /usr/bin/find / -type d (-fstype nfs -o fstype NFS -o fstype nfs3 -o
> -fstype afs -o -fstype proc -o -fstype smbfs -o -fstype autofs -o fstype
> iso9660 -o -fstype ncpfs -o fstype coda -o -fstype devpts -o -fstype
> ftpfs -o -fstype devfs -o -fstype mfs -o -fstype sysfs -o -fstype shfs
> -o -fstype cifs -o -fstype 9P -o regex
> -prune -print 0
Find all directories under / that not of certain filesystem types and don’t
match certain paths and output the result to SOMETHING you didn’t show.
So… this is incomplete. Find out the process that is getting fed this
information when it runs and it might make better sense. I’m guessing that
because of the -print 0, it might be getting fed to something like xargs -0
which in turn is going to run SOMETHING on the list of dirs. (but that’s
just a guess)
OK, how do I find that out? The Process Manager shows the PID of the find… Can I use that? I would not know how either though…
I’ll have to wait for the next time that happens though, it does every couple of days more or less… I think.
Personally, I’m a big locate fan; I use it to find files all the time, but some people never use it. For them, its useless, for me its vital.
A lot of people use ‘find’ directly, and that is versatile -it can do tricks that locate can never do- but it is slow for big searches. Locate, on the other hand, is fast, but simple.
Conventionally, an ‘updatedb’ is run at some quiet time -say at 03:00- but that doesn’t work if the computer is always off at that time. Of course, you can manually run ‘updatedb’ at a time of your choice, too.
Thanks everyone. These replies were all very helpful.
Well, the crontab file itself is not empty, just nothing is scheduled. Everything is working normally.
Never used locate, so I’m guessing uninstalling it is my best bet. I do use ‘find’ but extremely rarely.
I’m extremely organized, so searching on my own computer is something of a rarity. When I was on the Google Desktop development team I was one of only two who did not use our own product!
Searching for files simple has never be a common use-case for me. I can’t reorganize the web, so I still search there
This could be a bad sector somewhere on the drive, Linux will try to read data until it succeeds or the end of time which ever comes first. This causes the drive to tick and the system to freeze. So please check the hardware.