Bug 186540
Summary: | request: could mlocate be updated to use inotify? | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Hunt <jamesodhunt> |
Component: | mlocate | Assignee: | Miloslav Trmač <mitr> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | Keywords: | FutureFeature |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-03-24 14:02:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James Hunt
2006-03-24 08:26:01 UTC
Thanks for the suggestion, but inotify isn't really suitable for such global watching. 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 anyway. 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.) |