lmuserx4849 wrote: ⤴
Sun Apr 22, 2018 11:17 am
Your issue piqued my interest. I use locate a lot because it indexes the "entire" system into a database. Sometimes after an install I'll run it. It should run in the background, unnoticed. find transverses the file system in real-time, and can be slower.
I found this: updatedb.mlocate uses 100% of the hdd IO. The OS is completely unusable.
It talks about PRUNEPATHS.
My contents of /etc/updatedb.conf:
PRUNEPATHS="/mnt /cdrom /tmp /usr/tmp /var/tmp /var/spool /proc /media /sys /data /home/.ecryptfs"
PRUNEFS="NFS nfs nfs4 rpc_pipefs afs binfmt_misc proc smbfs autofs iso9660 ncpfs coda devpts ftpfs devfs mfs shfs sysfs cifs lustre tmpfs usbfs udf fuse.glusterfs fuse.sshfs curlftpfs ecryptfs fusesmb devtmpfs"
To be honest, three days ago I didn't know that
existed, I discovered its existence because of the I/O bandwith the indexing used everyday.
is good to specify the directories desired to not be indexed, but the problem is that I don't like the system being indexed by a command I don't use. I understand you prefer to use
, we all have our "ol' reliable", and mine is
. It's true it's slower, but I use
to find files not only by their name and to do things with them with
. As far as I'm aware,
is not able to do so, so
is not the appropriate utility for me. Which doesn't mean it's not for you or for anyone else.
Of course, there are more differences between
. For those who are interested and, like me, didn't know about the existence of locate, here's a good comparison of them