mirror of https://github.com/mkerrisk/man-pages
inotify.7: Remind reader of the cookie value in discussion of rename events
Reported-by: Jan Kara <jack@suse.cz> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
6f1a495406
commit
fa51f4d941
|
@ -652,14 +652,17 @@ create a new inotify file descriptor,
|
|||
and then re-create watches and cache entries
|
||||
for the objects to be monitored.)
|
||||
.SS Dealing with rename() events
|
||||
The
|
||||
As noted above, the
|
||||
.B IN_MOVED_FROM
|
||||
and
|
||||
.B IN_MOVED_TO
|
||||
events that are generated by
|
||||
event pair that is generated by
|
||||
.BR rename (2)
|
||||
are usually available as consecutive events when reading
|
||||
from the inotify file descriptor.
|
||||
can be matched up via their shared cookie value.
|
||||
However, the task of matching has some challenges.
|
||||
|
||||
These two events are usually consecutive in the event stream available
|
||||
when reading from the inotify file descriptor.
|
||||
However, this is not guaranteed.
|
||||
If multiple processes are triggering events for monitored objects,
|
||||
then (on rare occasions) an arbitrary number of
|
||||
|
|
Loading…
Reference in New Issue