fanotify.7: Minor fixes

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-04-25 09:20:45 +02:00
parent d9b086d625
commit 6d8c5d015d
1 changed files with 8 additions and 8 deletions

View File

@ -167,11 +167,11 @@ Therefore, and for performance reasons, it is recommended to use a larger
buffer size when reading, for example 4096 bytes.
.TP
.I vers
This field holds a version number for the structures.
This field holds a version number for the structure.
It must be compared to
.B FANOTIFY_METADATA_VERSION
to verify that the structures at runtime match the structures at compile
time.
to verify that the structures returned at runtime match
the structures defined at compile time.
In case of a mismatch, the application should abandon trying to use the
fanotify file descriptor.
.TP
@ -193,9 +193,9 @@ This is an open file descriptor for the object being accessed, or
if a queue overflow occurred.
The file descriptor can be used to access the contents of the monitored file or
directory.
It has internal the flag
The
.B FMODE_NONOTIFY
set.
file status flag is set on the corresponding open file description.
This flag suppresses fanotify event generation.
Hence, when the receiver of the fanotify event accesses the notified file or
directory using this file descriptor, no additional events will be created.
@ -231,7 +231,7 @@ or
was closed.
.TP
.B FAN_CLOSE_NOWRITE
A file that was only opened for reading
A file that was opened read-only
.RB ( O_RDONLY )
or a directory was closed.
.TP
@ -262,7 +262,7 @@ A file was closed
(FAN_CLOSE_WRITE | FAN_CLOSE_NOWRITE).
.PP
The following macros are provided to iterate over a buffer containing fanotify
event metadata returned by
event metadata returned by a
.BR read (2)
from an fanotify file descriptor.
.TP
@ -365,7 +365,7 @@ was specified in the
.I event_f_flags
argument when calling
.BR fanotify_init (2)
and the event occured for a monitored file that is currently being execuded.
and the event occurred for a monitored file that is currently being execuded.
.PP
In addition to the usual errors for
.BR write (2),