Bug 186540 - request: could mlocate be updated to use inotify?
request: could mlocate be updated to use inotify?
Product: Fedora
Classification: Fedora
Component: mlocate (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Miloslav Trmač
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2006-03-24 03:26 EST by James Hunt
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-24 09:02:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description James Hunt 2006-03-24 03:26:01 EST
Description of problem:

Could mlocate be updated to use inotify to remove the need for even running

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Miloslav Trmač 2006-03-24 09:02:21 EST
Thanks for the suggestion, but inotify isn't really suitable for such global

First, inotify doesn't work over network filesystems, so it isn't possible to
guarantee instantaneous update in general, and a periodic scan is necessary

Second, inodes of all watched directories have to be kept in memory; on my
laptop that would be roughly 16000 inodes, which is about 10 MB of memory
wasted for locate; consider a file server with a few terabytes of storage.
(To prevent this pinning of kernel memory, inotify has a configurable limit
on the number of watches, which is 8192 by default.)

Note You need to log in before you can comment on or make changes to this bug.