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
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

If 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
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.

Loading...