Gregg wrote:
>
> Anyone know why slocate might start without my asking? My mp3s sounded like
> they had the hiccups so I looked at the processes running - two slocates
> had been running and chewing up about 33% of the cpu each.
>
> The amount of time they had been running leads me to belive that I didn't
> start them and after thinking about it, may have started on the roll over.
> Anyone else get this (RH6.0)??
I've had problems with slocate hanging on vfat partitions.
A workaround is to disable scanning of the VFAT partitions:
1.Edit /etc/updatedb.conf
Add the mountpoints of the VFAT partitions to the EXCLUDE line:
EXCLUDE="/proc,/tmp/,/var/tmp,/usr/tmp,/net,/afs,/dosc,/dosd"
2.Edit /etc/cron.daily/slocate.cron
Add the VFAT partitions to the -e option to /usr/bin/slocate:
/usr/bin/slocate -u -e /tmp -e
"/var/tmp,/usr/tmp,/afs,/net,/proc,/dosc,/dosd";
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
