inotify.7: A monitoring process can't easily distinguish events triggered by itself

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2013-02-25 07:48:02 +01:00
parent 0649de17bd
commit 99e603bd3f
1 changed files with 5 additions and 1 deletions

View File

@ -23,7 +23,7 @@
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
.TH INOTIFY 7 2012-04-26 "Linux" "Linux Programmer's Manual"
.TH INOTIFY 7 2013-02-25 "Linux" "Linux Programmer's Manual"
.SH NAME
inotify \- monitoring file system events
.SH DESCRIPTION
@ -409,6 +409,10 @@ This can take a significant amount time for large directory trees.
The inotify API provides no information about the user or process that
triggered the inotify event.
In particular, there is no easy
way for a process that is monitoring events via inotify
to distinguish events that it triggers
itself from those that are triggered by other processes.
Note that the event queue can overflow.
In this case, events are lost.