From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MZLnM-0005u2-D1 for garchives@archives.gentoo.org; Fri, 07 Aug 2009 09:31:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EDFABE02C1; Fri, 7 Aug 2009 09:31:26 +0000 (UTC) Received: from mail.allt1.se (mail.allt1.se [85.8.30.10]) by pigeon.gentoo.org (Postfix) with ESMTP id B16D3E02C1 for ; Fri, 7 Aug 2009 09:31:26 +0000 (UTC) Received: by mail.allt1.se (Postfix, from userid 1002) id B0E64165953; Fri, 7 Aug 2009 11:28:36 +0200 (CEST) Received: from [192.168.1.100] (71.57.227.87.static.th.siw.siwnet.net [87.227.57.71]) by mail.allt1.se (Postfix) with ESMTP id 05FF9163615 for ; Fri, 7 Aug 2009 11:28:35 +0200 (CEST) Message-ID: <4A7BF46A.8090509@coolmail.se> Date: Fri, 07 Aug 2009 11:31:22 +0200 From: pk User-Agent: Thunderbird 2.0.0.22 (X11/20090625) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Weird slocate behaviour - file ignored? References: <6AF8CEA7-7B7D-4B6A-818F-7DD7410013D3@stellar.eclipse.co.uk> <617BA82A-0E5E-4489-A4E5-1475B9CC258E@stellar.eclipse.co.uk> In-Reply-To: <617BA82A-0E5E-4489-A4E5-1475B9CC258E@stellar.eclipse.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 96e8b7df-70e6-4591-b544-ddd245435cb6 X-Archives-Hash: ed9478dd5cb647bffcaace0082f8321f 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