mirror of https://github.com/mkerrisk/man-pages
inotify.7: Inotify doesn't work for remote and pseudo filesystems
Reported-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
fa51f4d941
commit
e226bed757
|
@ -617,6 +617,19 @@ way for a process that is monitoring events via inotify
|
||||||
to distinguish events that it triggers
|
to distinguish events that it triggers
|
||||||
itself from those that are triggered by other processes.
|
itself from those that are triggered by other processes.
|
||||||
|
|
||||||
|
Inotify reports only events that a user-space program triggers through
|
||||||
|
the filesystem API.
|
||||||
|
As a result, it does not catch remote events that occur
|
||||||
|
on network filesystems.
|
||||||
|
(Applications must fall back to polling the filesystem
|
||||||
|
to catch such events.)
|
||||||
|
Furthermore, various pseudo-filesystems such as
|
||||||
|
.IR /proc ,
|
||||||
|
.IR /sys ,
|
||||||
|
and
|
||||||
|
.IR /dev/pts
|
||||||
|
are not monitorable with inotify.
|
||||||
|
|
||||||
The inotify API identifies affected files by filename.
|
The inotify API identifies affected files by filename.
|
||||||
However, by the time an application processes an inotify event,
|
However, by the time an application processes an inotify event,
|
||||||
the filename may already have been deleted or renamed.
|
the filename may already have been deleted or renamed.
|
||||||
|
|
Loading…
Reference in New Issue