Carl Lowenstein wrote: > On 8/17/07, Gus Wirth <[EMAIL PROTECTED]> wrote: >> Carl Lowenstein wrote: >> [snip] >>> $ locate --version >>> Secure Locate 2.7 - Released January 24, 2003 >>> >>> That's how I just spent Friday afternoon. If anybody wants more >>> explanation of the command-line stuff, I will supply it. >>> >>> Late-breaking news, from another Google exercise, this time looking >>> for "updatedb" not "locate" or "slocate". >>> >>> "GNU findutils does have largefile support as of 4.1.5." >>> >>> Bah. >> Fedora 5 has mlocate, which is different from both but tries to be >> compatible. It is written by Miloslav Trmac of Redhat. It doesn't seem >> to have any file size issues. >> > > 1) I don't see why the combination "updatedb/slocate" should care > about file sizes, since it is only asked to create and search a list > of file names. > > 2) Unfortunately the slocate database /var/locate/slocate.db and the > mlocate database /var/lib/mlocate/mlocate.db are not compatible with > one another, so I can't tell easily whether the problem is in the > creation of the database or the searching. > > 3) I copied the two edge-case DVD images (just under 2GB, just over > 2GB) to a FC6 system and ran /etc/cron.daily/mlocate.cron to produce a > new database. locate was able to find both files. So the problem has > indeed been solved in one or both of the two programs. > > $ mlocate --version > bash: mlocate: command not found > $ locate --version > mlocate 0.15 > > 4) I suppose it isn't worth the time and effort to "Use the Source", > but it would be sort of interesting to know why a program that deals > with file names should screw up because of file sizes.. >
Locate doesn't show files that do not exist any longer, or those that the user can't access because of perms. I have confirmed (in ubu 7.04 32bit) the behavior you describe. Running an strace is informative: It shows calls to lstat64 and access. On a 64bit f7, there are calls to access, but not any lstat. I bet a look at the code in the vicinity of the lstat64 call might show a variable type mismatch. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
