fanotify_mark.2: Clarification about FAN_EVENT_ON_CHILD and new events

Some of the new event types that were added in v5.1 along with
init flag FAN_REPORT_FID are not eligible for reporting to a
directory watching with FAN_EVENT_ON_CHILD.

Document the events that cannot be generated on children of a
watching parent.

Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Reviewed-by: Matthew Bobrowski <mbobrowski@mbobrowski.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Amir Goldstein 2020-04-20 21:42:57 +03:00 committed by Michael Kerrisk
parent d71c9b4a5c
commit 1f20a88032
1 changed files with 14 additions and 1 deletions

View File

@ -314,8 +314,21 @@ Events for the immediate children of marked directories shall be created.
The flag has no effect when marking mounts and filesystems.
Note that events are not generated for children of the subdirectories
of marked directories.
More specifically, the directory entry modification events
.BR FAN_CREATE ,
.BR FAN_DELETE ,
.BR FAN_MOVED_FROM
and
.BR FAN_MOVED_TO
are not generated for any entry modifications performed inside subdirectories
of marked directories.
Note that the events
.BR FAN_DELETE_SELF
and
.BR FAN_MOVE_SELF
are not generated for children of marked directories.
To monitor complete directory trees it is necessary to mark the relevant
mount.
mount or filesystem.
.PP
The following composed values are defined:
.TP