Noticed a strange thing that happens randomly on my SuSE9.2

Sequence of events:

1. Boot up computer.
2. Start Juk to play some ogg.
3. Start LBreakout and play.
- noticed that the graphics is jerky.
4. Start Konsole and issue TOP command
- noticed that the FIND command is listed as taking sometimes up to 90% of the CPU.
5. Try to issue KILL command with the process id, but process cannot be killed.

In cases where I start the above sequence and there is no jerky graphics, the FIND command is not there. So I can sort of say the FIND command is causing this problem.

What is this FIND command?
Since I did not started it, how does it starts by itself?
How can I disable it so that it does not starts by itself?
If started, how to kill it ?

Appreciate any advise.

The find command (as the name already says) searches and finds files on your system. If you look at the process tree (I am not sure how this works on command line, but ksysguard offers this option), you will probably see that 'find' runs as a daughter-process of something like updatedb or mandb. These are invoked by cron and update your file/manfile databases. Especially if you have the package findutils-locate installed, the system will be regulary screen for new files. To avoid this, you need to move the script 'updatedb' from /etc/cron.daily to another schedule (e.g. /etc/cron.weekly) or delete it totally. You may want to do the same with 'do_mandb'.