Bug#2791: locate seg faults if locatedb too big
Could you save the /var/lib/locate/locatedb file for me? Perhaps make
it available for anonymous ftp so that I can duplicate the problem.
If so, then I may be able to duplicate the problem.
This was an old bug under findutils, but I was unable to reproduce the
bug, the original submitter and the debian-devel list did not respond
to my request. I'm glad to finally get a real live bug.
I'll try to address the configuration issue later.
kevin@aimnet.com
>>>>> "Craig" == Craig Sanders <cas@muffin.pronet.com> writes:
Craig> Package: findutils Version: 4.1-9
Craig> locate seg faults when the /var/lib/locate/locatedb file is too
Craig> big.
Craig> I don't know how big "too big" is.
Craig> I just upgraded findutils to the latest version, and forgot to
Craig> hack /usr/bin/updatedb to exclude "-fstype iso9660",
Craig> "/usr*/spool", and "/usr3/httpd/cache" (i don't want my cdrom
Craig> drive indexed, and i dont want my news spool or web cache
Craig> indexed either).
Craig> next time i tried to locate a file, locate crashed part way
Craig> through displaying the matching files.
Craig> I remembered that the same thing had happened with previous
Craig> versions of locate, hacked the updatedb to exclude my news
Craig> spool, web cache, and cdrom and ran updatedb again. After
Craig> that, locate worked with no problems.
Craig> BTW, maybe this should go in a separate bug report, but I think
Craig> that the configuration for updatedb should go in a separate
Craig> config file (maybe /var/lib/locate/config), so that I don't
Craig> lose the config whenever I upgrade findutils.
Reply to: