From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Things that need to be fixed: | Things that need to be fixed: | ||
* | * Ignore masks, so that events on files can be ignored until the files are modified | ||
* Reliable vs. non-reliable delivery | * Reliable vs. non-reliable delivery | ||
* | * Support for access decisions | ||
* | * Per mount point notification (general subtree notification seems too hard) | ||
** Clarify how mount point marks should propagate to new mounts from parent mounts, when creating a new bind mount, and to existing bind mounts. | |||
* Include uid, not just pid | * Include uid, not just pid | ||
Probably for the next round: | |||
* Add a flag to turn off event merging (or make merging less aggressive) so that events will happen "in order"? | |||
* Support non-root users (will require permission checks) | |||
* Support directory events by passing an fd to the directory | * Support directory events by passing an fd to the directory | ||
* | ** Allow users to get a wd instead of an fd if desired (please explain!) | ||
Revision as of 10:55, 21 October 2009
Things that need to be fixed:
- Ignore masks, so that events on files can be ignored until the files are modified
- Reliable vs. non-reliable delivery
- Support for access decisions
- Per mount point notification (general subtree notification seems too hard)
- Clarify how mount point marks should propagate to new mounts from parent mounts, when creating a new bind mount, and to existing bind mounts.
- Include uid, not just pid
Probably for the next round:
- Add a flag to turn off event merging (or make merging less aggressive) so that events will happen "in order"?
- Support non-root users (will require permission checks)
- Support directory events by passing an fd to the directory
- Allow users to get a wd instead of an fd if desired (please explain!)