Stroller wrote: > I'm seeing on a SECOND machine exactly the same thing - files larger > than about 4gb are not showing up in the locate search results: > > $ ls -lh File.big > -rw-r--r-- 1 stroller users 5.4G 2009-02-27 10:31 File.big > $ sudo updatedb -v > foo > Password: > $ grep File.big foo > /home/stroller/File.big > $ locate File.big > $
I get the same behaviour as you: # updatedb -v | grep -i file.big /home/pk/file.big # locate file.big # Files below that ~4Gb shows up as normal... I have nothing out of the ordinary in my updatedb.conf either: # /etc/updatedb.conf: config file for slocate # $Id: updatedb.conf,v 1.25 2008/12/02 20:09:15 vapier Exp $ # This file sets variables that are used by updatedb. # For more info, see the updatedb(1) manpage. # Filesystems that are pruned from updatedb database PRUNEFS="afs auto autofs cifs devfs devpts eventpollfs futexfs gfs hugetlbfs iso9660 mqueue ncpfs nfs NFS nfs4 nfsd nnpfs ocfs ocfs2 pipefs proc ramfs rpc_pipefs selinuxfs sfs shfs smbfs sockfs spufs subfs supermount sysfs tmpfs udf usbfs vperfctrfs" # Paths which are pruned from updatedb database PRUNEPATHS="/tmp /var/tmp /root/.ccache" # nice value to run at: see -n in nice(1) NICE="10" # ionice class to run at: see -c in ionice(1) IONICE_CLASS="2" # ionice priority to run at: see -n in ionice(1) IONICE_PRIORITY="7" So why does it prune files with bigger size than about 4Gb? The only thing I can think of is that my machine is 32bit... But why would slocate use file size as a factor? Best regards Peter K
