Do you have a FAT or FAT32 partition mounted anywhere? If so, I think you
can fix this by
First: killing the offending process (`killall slocate`)
Second: Telling updatedb to ignore that partition in the future
(edit /etc/updatedb.conf and add the mount point of the FAT
partition to the EXCLUDE section)
I had this same problem and telling updatedb/slocate to exclude the FAT
partition fixed it.
-Matt
On Tue, 27 Jul 1999, Dominique Deleris wrote:
> Hi list.
>
> I have launched updatedb as root, and now I have a process (slocate)
> that has been running for 25 minutes, consuming 80-90 % cpu-time, and
> that does not seem to come to an end.
>
> I've cheked my /var/lib/slocate directory, and it shows :
>
> -rw-r--r-- 1 root root 0 Jul 27 21:51 slocate.db
> -rw-r----- 1 root slocate 49410 Jul 27 21:52 slocate.db.tmp
>
> What's happening ?
>
> Thanks for your help.
>
> Dominique
>
