2006-02-08 04:13:22 +00:00
|
|
|
'\" t
|
|
|
|
.\" Hey Emacs! This file is -*- nroff -*- source.
|
|
|
|
.\"
|
2007-09-20 06:52:22 +00:00
|
|
|
.\" Copyright (C) 2006 Michael Kerrisk <mtk.manpages@gmail.com>
|
2006-02-08 04:13:22 +00:00
|
|
|
.\"
|
|
|
|
.\" Permission is granted to make and distribute verbatim copies of this
|
|
|
|
.\" manual provided the copyright notice and this permission notice are
|
|
|
|
.\" preserved on all copies.
|
|
|
|
.\"
|
|
|
|
.\" Permission is granted to copy and distribute modified versions of this
|
|
|
|
.\" manual under the conditions for verbatim copying, provided that the
|
|
|
|
.\" entire resulting derived work is distributed under the terms of a
|
|
|
|
.\" permission notice identical to this one.
|
2007-04-12 22:42:49 +00:00
|
|
|
.\"
|
2006-02-08 04:13:22 +00:00
|
|
|
.\" Since the Linux kernel and libraries are constantly changing, this
|
|
|
|
.\" manual page may be incorrect or out-of-date. The author(s) assume no
|
|
|
|
.\" responsibility for errors or omissions, or for damages resulting from
|
2008-03-18 14:47:54 +00:00
|
|
|
.\" the use of the information contained herein. The author(s) may not
|
|
|
|
.\" have taken the same level of care in the production of this manual,
|
|
|
|
.\" which is licensed free of charge, as they might when working
|
|
|
|
.\" professionally.
|
2007-04-12 22:42:49 +00:00
|
|
|
.\"
|
2006-02-08 04:13:22 +00:00
|
|
|
.\" Formatted or processed versions of this manual, if unaccompanied by
|
|
|
|
.\" the source, must acknowledge the copyright and authors of this work.
|
|
|
|
.\"
|
2008-11-18 15:44:09 +00:00
|
|
|
.TH INOTIFY 7 2008-11-18 "Linux" "Linux Programmer's Manual"
|
2006-02-08 04:13:22 +00:00
|
|
|
.SH NAME
|
2006-02-10 05:20:27 +00:00
|
|
|
inotify \- monitoring file system events
|
2006-02-08 04:13:22 +00:00
|
|
|
.SH DESCRIPTION
|
|
|
|
The
|
2007-04-12 22:42:49 +00:00
|
|
|
.I inotify
|
2006-02-08 04:13:22 +00:00
|
|
|
API provides a mechanism for monitoring file system events.
|
|
|
|
Inotify can be used to monitor individual files,
|
|
|
|
or to monitor directories.
|
|
|
|
When a directory is monitored, inotify will return events
|
|
|
|
for the directory itself, and for files inside the directory.
|
|
|
|
|
2007-04-12 22:42:49 +00:00
|
|
|
The following system calls are used with this API:
|
2008-10-10 11:30:18 +00:00
|
|
|
.BR inotify_init (2)
|
2008-10-29 20:43:44 +00:00
|
|
|
(or
|
2008-10-10 11:30:18 +00:00
|
|
|
.BR inotify_init1 (2)),
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR inotify_add_watch (2),
|
|
|
|
.BR inotify_rm_watch (2),
|
|
|
|
.BR read (2),
|
2007-04-12 22:42:49 +00:00
|
|
|
and
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR close (2).
|
2006-02-08 04:13:22 +00:00
|
|
|
|
|
|
|
.BR inotify_init (2)
|
2007-04-12 22:42:49 +00:00
|
|
|
creates an inotify instance and returns a file descriptor
|
2006-06-05 08:16:20 +00:00
|
|
|
referring to the inotify instance.
|
2008-10-10 11:30:18 +00:00
|
|
|
The more recent
|
|
|
|
.BR inotify_init1 (2)
|
|
|
|
is like
|
|
|
|
.BR inotify_init (2),
|
|
|
|
but provides some extra functionality.
|
2006-02-08 04:13:22 +00:00
|
|
|
|
|
|
|
.BR inotify_add_watch (2)
|
2006-06-05 08:16:20 +00:00
|
|
|
manipulates the "watch list" associated with an inotify instance.
|
2006-02-10 05:25:30 +00:00
|
|
|
Each item ("watch") in the watch list specifies the pathname of
|
2007-04-12 22:42:49 +00:00
|
|
|
a file or directory,
|
2006-02-08 04:13:22 +00:00
|
|
|
along with some set of events that the kernel should monitor for the
|
|
|
|
file referred to by that pathname.
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR inotify_add_watch (2)
|
2006-02-08 04:13:22 +00:00
|
|
|
either creates a new watch item, or modifies an existing watch.
|
|
|
|
Each watch has a unique "watch descriptor", an integer
|
|
|
|
returned by
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR inotify_add_watch (2)
|
2006-02-08 04:13:22 +00:00
|
|
|
when the watch is created.
|
|
|
|
|
|
|
|
.BR inotify_rm_watch (2)
|
|
|
|
removes an item from an inotify watch list.
|
|
|
|
|
2007-04-12 22:42:49 +00:00
|
|
|
When all file descriptors referring to an inotify
|
2006-06-05 08:16:20 +00:00
|
|
|
instance have been closed,
|
2007-04-12 22:42:49 +00:00
|
|
|
the underlying object and its resources are
|
close.2, epoll_create.2, epoll_ctl.2, fcntl.2, madvise.2, mmap.2, mremap.2, select_tut.2, setgid.2, setuid.2, syscalls.2, vmsplice.2, dlopen.3, fts.3, getpw.3, stdio.3, fd.4, initrd.4, random.4, sd.4, bootparam.7, capabilities.7, cpuset.7, epoll.7, inotify.7, man.7, socket.7, x25.7: Global fix: s/re-/re/
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "re-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2010-01-16 17:45:23 +00:00
|
|
|
freed for reuse by the kernel;
|
2006-02-08 04:13:22 +00:00
|
|
|
all associated watches are automatically freed.
|
|
|
|
|
|
|
|
To determine what events have occurred, an application
|
|
|
|
.BR read (2)s
|
|
|
|
from the inotify file descriptor.
|
2007-04-12 22:42:49 +00:00
|
|
|
If no events have so far occurred, then,
|
2006-03-01 23:13:12 +00:00
|
|
|
assuming a blocking file descriptor,
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR read (2)
|
2008-07-04 15:50:36 +00:00
|
|
|
will block until at least one event occurs
|
|
|
|
(unless interrupted by a signal,
|
|
|
|
in which case the call fails with the error
|
|
|
|
.BR EINTR ;
|
|
|
|
see
|
|
|
|
.BR signal (7)).
|
2006-02-08 04:13:22 +00:00
|
|
|
|
|
|
|
Each successful
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR read (2)
|
2006-02-08 04:13:22 +00:00
|
|
|
returns a buffer containing one or more of the following structures:
|
2007-12-19 05:53:30 +00:00
|
|
|
.in +4n
|
2006-02-08 04:13:22 +00:00
|
|
|
.nf
|
|
|
|
|
|
|
|
struct inotify_event {
|
|
|
|
int wd; /* Watch descriptor */
|
2008-11-18 20:47:33 +00:00
|
|
|
.\" FIXME . The type of the 'wd' field should probably be "int32_t".
|
|
|
|
.\" I submitted a patch to fix this. See the LKML thread
|
|
|
|
.\" "[patch] Fix type errors in inotify interfaces", 18 Nov 2008
|
2008-11-20 15:24:10 +00:00
|
|
|
.\" Glibc bug filed: http://sources.redhat.com/bugzilla/show_bug.cgi?id=7040
|
2006-02-08 04:13:22 +00:00
|
|
|
uint32_t mask; /* Mask of events */
|
2007-04-12 22:42:49 +00:00
|
|
|
uint32_t cookie; /* Unique cookie associating related
|
2006-02-08 04:13:22 +00:00
|
|
|
events (for rename(2)) */
|
2008-06-05 20:14:50 +00:00
|
|
|
uint32_t len; /* Size of \fIname\fP field */
|
2006-02-08 04:13:22 +00:00
|
|
|
char name[]; /* Optional null-terminated name */
|
|
|
|
};
|
|
|
|
.fi
|
2007-12-19 05:53:30 +00:00
|
|
|
.in
|
2006-02-08 04:13:22 +00:00
|
|
|
|
|
|
|
.I wd
|
|
|
|
identifies the watch for which this event occurs.
|
2007-04-12 22:42:49 +00:00
|
|
|
It is one of the watch descriptors returned by a previous call to
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR inotify_add_watch (2).
|
2006-02-08 04:13:22 +00:00
|
|
|
|
|
|
|
.I mask
|
|
|
|
contains bits that describe the event that occurred (see below).
|
|
|
|
|
|
|
|
.I cookie
|
|
|
|
is a unique integer that connects related events.
|
|
|
|
Currently this is only used for rename events, and
|
|
|
|
allows the resulting pair of
|
|
|
|
.B IN_MOVE_FROM
|
2007-04-12 22:42:49 +00:00
|
|
|
and
|
2006-02-08 04:13:22 +00:00
|
|
|
.B IN_MOVE_TO
|
|
|
|
events to be connected by the application.
|
|
|
|
|
2007-04-12 22:42:49 +00:00
|
|
|
The
|
2006-02-08 04:13:22 +00:00
|
|
|
.I name
|
|
|
|
field is only present when an event is returned
|
2007-04-12 22:42:49 +00:00
|
|
|
for a file inside a watched directory;
|
2006-02-08 04:13:22 +00:00
|
|
|
it identifies the file pathname relative to the watched directory.
|
2007-04-12 22:42:49 +00:00
|
|
|
This pathname is null-terminated,
|
2006-02-08 19:16:12 +00:00
|
|
|
and may include further null bytes to align subsequent reads to a
|
2006-02-08 04:13:22 +00:00
|
|
|
suitable address boundary.
|
|
|
|
|
|
|
|
The
|
|
|
|
.I len
|
2007-04-12 22:42:49 +00:00
|
|
|
field counts all of the bytes in
|
2006-02-08 04:13:22 +00:00
|
|
|
.IR name ,
|
2007-04-12 22:42:49 +00:00
|
|
|
including the null bytes;
|
2006-02-08 04:13:22 +00:00
|
|
|
the length of each
|
|
|
|
.I inotify_event
|
|
|
|
structure is thus
|
|
|
|
.IR "sizeof(inotify_event)+len" .
|
2007-05-27 14:21:25 +00:00
|
|
|
|
2007-06-21 22:55:04 +00:00
|
|
|
The behavior when the buffer given to
|
2007-05-27 14:21:25 +00:00
|
|
|
.BR read (2)
|
2007-06-21 22:55:04 +00:00
|
|
|
is too small to return information about the next event depends
|
2007-05-27 14:21:25 +00:00
|
|
|
on the kernel version: in kernels before 2.6.21,
|
|
|
|
.BR read (2)
|
|
|
|
returns 0; since kernel 2.6.21,
|
|
|
|
.BR read (2)
|
|
|
|
fails with the error
|
|
|
|
.BR EINVAL .
|
2006-02-08 04:13:22 +00:00
|
|
|
.SS inotify events
|
2007-04-12 22:42:49 +00:00
|
|
|
The
|
2006-02-08 04:13:22 +00:00
|
|
|
.BR inotify_add_watch (2)
|
|
|
|
.I mask
|
2007-04-12 22:42:49 +00:00
|
|
|
argument and the
|
2006-02-08 04:13:22 +00:00
|
|
|
.I mask
|
|
|
|
field of the
|
|
|
|
.I inotify_event
|
|
|
|
structure returned when
|
|
|
|
.BR read (2)ing
|
|
|
|
an inotify file descriptor are both bit masks identifying
|
|
|
|
inotify events.
|
|
|
|
The following bits can be specified in
|
|
|
|
.I mask
|
|
|
|
when calling
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR inotify_add_watch (2)
|
2007-04-12 22:42:49 +00:00
|
|
|
and may be returned in the
|
2006-02-08 04:13:22 +00:00
|
|
|
.I mask
|
|
|
|
field returned by
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR read (2):
|
2008-01-13 09:29:25 +00:00
|
|
|
.RS 4
|
|
|
|
.sp
|
|
|
|
.PD 0
|
|
|
|
.TP 18
|
|
|
|
.B IN_ACCESS
|
|
|
|
File was accessed (read) (*).
|
|
|
|
.TP
|
|
|
|
.B IN_ATTRIB
|
2008-05-09 13:24:51 +00:00
|
|
|
Metadata changed, e.g., permissions, timestamps, extended attributes,
|
|
|
|
link count (since Linux 2.6.25), UID, GID, etc. (*).
|
2008-01-13 09:29:25 +00:00
|
|
|
.TP
|
|
|
|
.B IN_CLOSE_WRITE
|
|
|
|
File opened for writing was closed (*).
|
|
|
|
.TP
|
|
|
|
.B IN_CLOSE_NOWRITE
|
|
|
|
File not opened for writing was closed (*).
|
|
|
|
.TP
|
|
|
|
.B IN_CREATE
|
|
|
|
File/directory created in watched directory (*).
|
|
|
|
.TP
|
|
|
|
.B IN_DELETE
|
|
|
|
File/directory deleted from watched directory (*).
|
|
|
|
.TP
|
|
|
|
.B IN_DELETE_SELF
|
|
|
|
Watched file/directory was itself deleted.
|
|
|
|
.TP
|
|
|
|
.B IN_MODIFY
|
|
|
|
File was modified (*).
|
|
|
|
.TP
|
|
|
|
.B IN_MOVE_SELF
|
|
|
|
Watched file/directory was itself moved.
|
|
|
|
.TP
|
|
|
|
.B IN_MOVED_FROM
|
|
|
|
File moved out of watched directory (*).
|
|
|
|
.TP
|
|
|
|
.B IN_MOVED_TO
|
|
|
|
File moved into watched directory (*).
|
|
|
|
.TP
|
|
|
|
.B IN_OPEN
|
|
|
|
File was opened (*).
|
|
|
|
.PD
|
|
|
|
.RE
|
2006-02-08 04:13:22 +00:00
|
|
|
.PP
|
2007-04-12 22:42:49 +00:00
|
|
|
When monitoring a directory,
|
|
|
|
the events marked with an asterisk (*) above can occur for
|
2006-02-08 04:13:22 +00:00
|
|
|
files in the directory, in which case the
|
|
|
|
.I name
|
|
|
|
field in the returned
|
|
|
|
.I inotify_event
|
|
|
|
structure identifies the name of the file within the directory.
|
|
|
|
.PP
|
|
|
|
The
|
|
|
|
.B IN_ALL_EVENTS
|
|
|
|
macro is defined as a bit mask of all of the above events.
|
|
|
|
This macro can be used as the
|
|
|
|
.I mask
|
|
|
|
argument when calling
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR inotify_add_watch (2).
|
2006-02-08 04:13:22 +00:00
|
|
|
|
|
|
|
Two additional convenience macros are
|
|
|
|
.BR IN_MOVE ,
|
|
|
|
which equates to
|
|
|
|
IN_MOVED_FROM|IN_MOVED_TO,
|
|
|
|
and
|
2007-09-20 16:26:31 +00:00
|
|
|
.B IN_CLOSE
|
2006-02-08 04:13:22 +00:00
|
|
|
which equates to
|
|
|
|
IN_CLOSE_WRITE|IN_CLOSE_NOWRITE.
|
|
|
|
.PP
|
2007-04-12 22:42:49 +00:00
|
|
|
The following further bits can be specified in
|
2006-02-08 04:13:22 +00:00
|
|
|
.I mask
|
|
|
|
when calling
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR inotify_add_watch (2):
|
2008-01-13 09:29:25 +00:00
|
|
|
.RS 4
|
|
|
|
.sp
|
|
|
|
.PD 0
|
|
|
|
.TP 18
|
2008-05-07 13:43:44 +00:00
|
|
|
.BR IN_DONT_FOLLOW " (since Linux 2.6.15)"
|
|
|
|
Don't dereference \fIpathname\fP if it is a symbolic link.
|
2008-01-13 09:15:10 +00:00
|
|
|
.TP
|
|
|
|
.B IN_MASK_ADD
|
|
|
|
Add (OR) events to watch mask for this pathname if
|
|
|
|
it already exists (instead of replacing mask).
|
|
|
|
.TP
|
|
|
|
.B IN_ONESHOT
|
|
|
|
Monitor \fIpathname\fP for one event, then remove from
|
|
|
|
watch list.
|
|
|
|
.TP
|
2008-05-07 13:43:44 +00:00
|
|
|
.BR IN_ONLYDIR " (since Linux 2.6.15)"
|
|
|
|
Only watch \fIpathname\fP if it is a directory.
|
2008-01-13 09:29:25 +00:00
|
|
|
.PD
|
|
|
|
.RE
|
2006-02-08 04:13:22 +00:00
|
|
|
.PP
|
|
|
|
The following bits may be set in the
|
|
|
|
.I mask
|
|
|
|
field returned by
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR read (2):
|
2008-01-13 09:29:25 +00:00
|
|
|
.RS 4
|
|
|
|
.sp
|
|
|
|
.PD 0
|
|
|
|
.TP 18
|
2008-01-13 09:15:10 +00:00
|
|
|
.B IN_IGNORED
|
|
|
|
Watch was removed explicitly (\fBinotify_rm_watch\fP(2))
|
|
|
|
or automatically (file was deleted, or file system was unmounted).
|
|
|
|
.TP
|
|
|
|
.B IN_ISDIR
|
|
|
|
Subject of this event is a directory.
|
|
|
|
.TP
|
|
|
|
.B IN_Q_OVERFLOW
|
|
|
|
Event queue overflowed (\fIwd\fP is \-1 for this event).
|
|
|
|
.TP
|
|
|
|
.B IN_UNMOUNT
|
|
|
|
File system containing watched object was unmounted.
|
2008-01-13 09:29:25 +00:00
|
|
|
.PD
|
|
|
|
.RE
|
2006-02-08 04:13:22 +00:00
|
|
|
.SS /proc interfaces
|
2007-04-12 22:42:49 +00:00
|
|
|
The following interfaces can be used to limit the amount of
|
2006-02-08 04:13:22 +00:00
|
|
|
kernel memory consumed by inotify:
|
|
|
|
.TP
|
2007-09-20 16:26:31 +00:00
|
|
|
.I /proc/sys/fs/inotify/max_queued_events
|
2006-02-08 04:13:22 +00:00
|
|
|
The value in this file is used when an application calls
|
|
|
|
.BR inotify_init (2)
|
2007-04-12 22:42:49 +00:00
|
|
|
to set an upper limit on the number of events that can be
|
2006-02-08 04:13:22 +00:00
|
|
|
queued to the corresponding inotify instance.
|
|
|
|
Events in excess of this limit are dropped, but an
|
|
|
|
.B IN_Q_OVERFLOW
|
|
|
|
event is always generated.
|
|
|
|
.TP
|
2007-09-20 16:26:31 +00:00
|
|
|
.I /proc/sys/fs/inotify/max_user_instances
|
2007-04-12 22:42:49 +00:00
|
|
|
This specifies an upper limit on the number of inotify instances
|
2006-02-08 04:13:22 +00:00
|
|
|
that can be created per real user ID.
|
|
|
|
.TP
|
2007-09-20 16:26:31 +00:00
|
|
|
.I /proc/sys/fs/inotify/max_user_watches
|
2008-11-18 15:44:09 +00:00
|
|
|
This specifies an upper limit on the number of watches
|
|
|
|
that can be created per real user ID.
|
2007-05-19 04:30:20 +00:00
|
|
|
.SH "VERSIONS"
|
|
|
|
Inotify was merged into the 2.6.13 Linux kernel.
|
|
|
|
The required library interfaces were added to glibc in version 2.4.
|
|
|
|
.RB ( IN_DONT_FOLLOW ,
|
|
|
|
.BR IN_MASK_ADD ,
|
|
|
|
and
|
|
|
|
.B IN_ONLYDIR
|
|
|
|
were only added in version 2.5.)
|
|
|
|
.SH "CONFORMING TO"
|
2007-12-25 21:28:09 +00:00
|
|
|
The inotify API is Linux-specific.
|
2006-02-08 04:13:22 +00:00
|
|
|
.SH "NOTES"
|
|
|
|
Inotify file descriptors can be monitored using
|
|
|
|
.BR select (2),
|
|
|
|
.BR poll (2),
|
2007-04-12 22:42:49 +00:00
|
|
|
and
|
2006-04-21 00:29:37 +00:00
|
|
|
.BR epoll (7).
|
2008-03-25 10:10:15 +00:00
|
|
|
When an event is available, the file descriptor indicates as readable.
|
|
|
|
|
|
|
|
Since Linux 2.6.25,
|
|
|
|
signal-driven I/O notification is available for inotify file descriptors;
|
|
|
|
see the discussion of
|
|
|
|
.B F_SETFL
|
|
|
|
(for setting the
|
|
|
|
.B O_ASYNC
|
|
|
|
flag),
|
|
|
|
.BR F_SETOWN ,
|
|
|
|
and
|
|
|
|
.B F_SETSIG
|
|
|
|
in
|
|
|
|
.BR fcntl (2).
|
|
|
|
The
|
|
|
|
.I siginfo_t
|
|
|
|
structure (described in
|
|
|
|
.BR sigaction (2))
|
|
|
|
that is passed to the signal handler has the following fields set:
|
|
|
|
.IR si_fd
|
|
|
|
is set to the inotify file descriptor number;
|
|
|
|
.IR si_signo
|
|
|
|
is set to the signal number;
|
|
|
|
.IR si_code
|
|
|
|
is set to
|
|
|
|
.BR POLL_IN ;
|
|
|
|
and
|
|
|
|
.B POLLIN
|
|
|
|
is set in
|
|
|
|
.IR si_band .
|
2006-02-08 04:13:22 +00:00
|
|
|
|
2007-04-12 22:42:49 +00:00
|
|
|
If successive output inotify events produced on the
|
|
|
|
inotify file descriptor are identical (same
|
|
|
|
.IR wd ,
|
|
|
|
.IR mask ,
|
2006-02-08 04:13:22 +00:00
|
|
|
.IR cookie ,
|
|
|
|
and
|
|
|
|
.IR name )
|
2008-08-27 04:21:29 +00:00
|
|
|
then they are coalesced into a single event if the
|
|
|
|
older event has not yet been read (but see BUGS).
|
2006-02-08 04:13:22 +00:00
|
|
|
|
2007-04-12 22:42:49 +00:00
|
|
|
The events returned by reading from an inotify file descriptor
|
|
|
|
form an ordered queue.
|
|
|
|
Thus, for example, it is guaranteed that when renaming from
|
|
|
|
one directory to another, events will be produced in the
|
2006-02-08 04:13:22 +00:00
|
|
|
correct order on the inotify file descriptor.
|
|
|
|
|
|
|
|
The
|
|
|
|
.B FIONREAD
|
2007-05-11 23:29:44 +00:00
|
|
|
.BR ioctl (2)
|
2007-04-12 22:42:49 +00:00
|
|
|
returns the number of bytes available to read from an
|
2006-02-08 04:13:22 +00:00
|
|
|
inotify file descriptor.
|
|
|
|
|
|
|
|
Inotify monitoring of directories is not recursive:
|
|
|
|
to monitor subdirectories under a directory,
|
|
|
|
additional watches must be created.
|
2006-06-05 11:00:07 +00:00
|
|
|
.SH "BUGS"
|
|
|
|
In kernels before 2.6.16, the
|
|
|
|
.B IN_ONESHOT
|
2007-04-12 22:42:49 +00:00
|
|
|
.I mask
|
2006-06-05 11:00:07 +00:00
|
|
|
flag does not work.
|
2008-08-27 04:21:29 +00:00
|
|
|
|
|
|
|
Before kernel 2.6.25,
|
2009-03-11 07:47:48 +00:00
|
|
|
the kernel code that was intended to coalesce successive identical events
|
2008-08-27 04:21:29 +00:00
|
|
|
(i.e., the two most recent events could potentially be coalesced
|
|
|
|
if the older had not yet been read)
|
|
|
|
instead checked if the most recent event could be coalesced with the
|
|
|
|
.I oldest
|
|
|
|
unread event.
|
2006-02-08 04:13:22 +00:00
|
|
|
.SH "SEE ALSO"
|
|
|
|
.BR inotify_add_watch (2),
|
|
|
|
.BR inotify_init (2),
|
2008-10-10 11:30:18 +00:00
|
|
|
.BR inotify_init1 (2),
|
2006-02-08 04:13:22 +00:00
|
|
|
.BR inotify_rm_watch (2),
|
|
|
|
.BR read (2),
|
|
|
|
.BR stat (2),
|
|
|
|
.IR Documentation/filesystems/inotify.txt .
|