inotify.7: Move discussion of application cache to start of "Limitations"

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-04-02 13:32:23 +02:00
parent 356911f692
commit 264276c6b0
1 changed files with 5 additions and 5 deletions

View File

@ -601,6 +601,11 @@ The
returns the number of bytes available to read from an
inotify file descriptor.
.SS Limitations and caveats
The inotify applications identifies events via watch descriptors.
It is the application's responsibility to cache a mapping
(if one is needed) between watch descriptors and pathnames.
Be aware that directory renamings may affect multiple cached pathnames.
Inotify monitoring of directories is not recursive:
to monitor subdirectories under a directory,
additional watches must be created.
@ -630,11 +635,6 @@ new files (and subdirectories) may already exist inside the subdirectory.
Therefore, you may want to scan the contents of the subdirectory
immediately after adding the watch (and, if desired,
recursively add watches for any subdirectories that it contains).
The inotify applications identifies events via watch descriptors.
It is the application's responsibility to cache a mapping
(if one is needed) between watch descriptors and pathnames.
Be aware that directory renamings may affect multiple cached pathnames.
.SH BUGS
.\" FIXME kernel commit 611da04f7a31b2208e838be55a42c7a1310ae321
.\" implies that unmount events were buggy 2.6.11 to 2.6.36