"find" Service Heavily Loads My Hdd

>Also, I haven't noticed substantial change in changing from version to version, including to 10.1, of SUSE.
We had no problems of this sort with Suse 10.0. They appeared exactly after upgrade to 10.1.

>Conclusion is, that the hardware alone is not the only determining factor.
Yes, this is true.

>Ultimately, you can get rid of automatic updating of the database - remove the script. You will, however, benefit substantally from the ability to issue "locate some_file".
Maybe moving the script to cron.weekly will help, let's wait and see

>However, if you say that even a powerful PC is slowed down, then maybe the updatedb is not the culprit.
The slowdown starts when find begins to work, and ends exactly when I kill the find service. Therefore, I have no grounds to blaim beagle, which is btw installed and used on all three computers.

>Probably it is worth looking at the modification date of the database before and after the slowdown; this may yield some answers. If I am not mistaken, the file is /var/lib/locatedb
I'll try that, thank you for your help!

Now I am suspecting that there is some trouble with the PC not related to updatedb, and the computer is not functioning at its full ability. Possible cause might be upgrading from 10.0, instead of fresh install.

Anyhow, let the updatedb run and finish at least once - don't kill that find.

OK, I changed the time in Yast, System, /etc/sysconfig editor, System, Cron, DAILY TIME, and set it to 04:00.
I changed the nice value of the job from -19 to 20 in file /etc/cron.daily/suse.de-updatedb.
And I moved the file from the directory cron.daily to cron.weekly.
So what, approx. at 15:45 my hdd got noisy, and the system became significantly slower. I checked in Ksysguard and saw that find and sort were running. They stopped at 15:59. I checked the file:///var/lib/locatedb, it was modified at 15:59.

OK, I changed the time in Yast, System, /etc/sysconfig editor, System, Cron, DAILY TIME, and set it to 04:00.
I changed the nice value of the job from -19 to 20 in file /etc/cron.daily/suse.de-updatedb.
And I moved the file from the directory cron.daily to cron.weekly.
So what, approx. at 15:45 my hdd got noisy, and the system became significantly slower. I checked in Ksysguard and saw that find and sort were running. They stopped at 15:59. I checked the file:///var/lib/locatedb, it was modified at 15:59.
[/b]

I think you did everything correctly, and I don't know why the cron job still ran. Did you reboot? - Maybe it is required after changes to system cron jobs.
You shall also check in file /etc/sysconfig/cron that the new time has been fixed in that file.

The duration of the update - 15 minutes - is about correct.

If you get a chance, try to get the process tree from Ksysguard - what process starts what process. The tree may change, but shall repeat itself, in about two-three variations. Does the process run with higher nice value (20) ?