fanotify.7: Move text describing fanotify_mark()

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-04-25 11:07:48 +02:00
parent 488cdd819c
commit 6c693f6de5
1 changed files with 7 additions and 7 deletions

View File

@ -47,7 +47,7 @@ The following system calls are used with this API:
.BR write (2),
and
.BR close (2).
.SS fanotify_init() and notification groups
.SS fanotify_init(), fanotify_mark(), and notification groups
The
.BR fanotify_init (2)
system call creates and initializes an fanotify notification group
@ -68,6 +68,12 @@ Having these two types of masks permits a mount point or directory to be
marked for receiving events, while at the same time ignoring events for
specific objects under that mount point or directory.
.PP
The
.BR fanotify_mark (2)
system call adds a file, directory, or mount to a notification group
and specifies which events
shall be reported (or ignored), or removes or modifies such an entry.
.PP
A possible usage of the ignore mask is for a file cache.
Events of interest for a file cache are modification of a file and closing
of the same.
@ -95,12 +101,6 @@ Permission events are requests to the receiving application to decide whether
permission for a file access shall be granted.
For these events, the recipient must write a response which decides whether
access is granted or not.
.SS fanotify_mark()
The
.BR fanotify_mark (2)
system call adds a file, directory, or mount to a notification group
and specifies which events
shall be reported (or ignored), or removes or modifies such an entry.
.SS Events, the event queue, and reading events
All events for an fanotify group are collected in a queue.
Consecutive events for the same filesystem object and originating from the