inotify-rs
inotify-rs copied to clipboard
Idiomatic inotify wrapper for the Rust programming language
(This includes changes from #134.) This adds an async `Inotify` type. It has an `async fn read_events` (close #121): ```rust pub async fn read_events io::Result
The documentation for `Inotify::event_stream` is out of date. 1. It talks about using an internal buffer, but it no longer does. 2. It could use examples showing the various usage...
Futures 0.3 will support the Async/Await syntax. One it reaches GA, Tokio will be next. We should investigate what it will require of us to support the new syntax and...
That would imply to use a select on the inotify's fd waiting for data in the fd or the timeout. The workaround would be to use the [nix crate](https://github.com/nix-rust/nix) with...
It is possible to create multiple `EventStream`s from a single `Inotify` instance. Those streams will `read` from the same inotify file descriptor. Depending on the timing of the reads, one...
When adding a watch using `Inotify::add_watch`, a `WatchMask` must be passed. This `WatchMask` defines which events should be watched and how to watch them. These two things, which events to...
From the inotify man page: > The set of watch descriptors that is being monitored via an inotify file descriptor can be viewed via the entry for the inotify file...
From reading the man pages, I get the impression that distinct event objects are generated for each type of event, and that therefore most bits in the event mask can't...
From the [inotify man page](http://man7.org/linux/man-pages/man7/inotify.7.html): > When a watch descriptor is removed by calling inotify_rm_watch(2) (or because a watch file is deleted or the filesystem that contains it is unmounted),...
Currently, a `WatchDescriptor` can exist pretty much independently of the actual inotify watch it represents. This means the user has to manually remove any watches (by calling `Inotify::rm_watch`) that they...