Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#8623 - unlike slocate, mlocate can return non-exisiting results.
Attached to Project:
Arch Linux
Opened by Hussam Al-Tayeb (hussam) - Monday, 12 November 2007, 18:03 GMT
Last edited by Aaron Griffin (phrakture) - Monday, 12 November 2007, 22:03 GMT
Opened by Hussam Al-Tayeb (hussam) - Monday, 12 November 2007, 18:03 GMT
Last edited by Aaron Griffin (phrakture) - Monday, 12 November 2007, 22:03 GMT
|
DetailsIf I remove a file after the last updatedb operation, mlocate still returns that file in it's search results.
This worked a lot better in slocate. Slocate didn't return non-existing results (files deleted after the last updatedb operation). i.e. mlocate returns, in it's results, files that are in the db but not existing anymore on the hard disk. Slocate ignores those non existing files when returning search results. |
This task depends upon
Closed by Aaron Griffin (phrakture)
Monday, 12 November 2007, 22:03 GMT
Reason for closing: Not a bug
Monday, 12 November 2007, 22:03 GMT
Reason for closing: Not a bug
Comment by Jan de Groot (JGC) -
Monday, 12 November 2007, 21:32 GMT
mlocate doesn't do this by default, but has a -e flag to have the same behaviour as you describe.