mirror of https://github.com/mkerrisk/man-pages
Added text describing what happens when the buffer given to read(2)
is too small to return information about the next event, and noting the behaviour change in 2.6.21.
This commit is contained in:
parent
78f2eeab03
commit
c7e3ee6faa
|
@ -20,7 +20,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 2006-02-07 "Linux 2.6.15" "Linux Programmer's Manual"
|
||||
.TH INOTIFY 7 2007-06-03 "Linux" "Linux Programmer's Manual"
|
||||
.SH NAME
|
||||
inotify \- monitoring file system events
|
||||
.SH DESCRIPTION
|
||||
|
@ -126,6 +126,16 @@ the length of each
|
|||
.I inotify_event
|
||||
structure is thus
|
||||
.IR "sizeof(inotify_event)+len" .
|
||||
|
||||
The behaviour when the buffer given to
|
||||
.BR read (2)
|
||||
is too small to return information about the next event depends
|
||||
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 .
|
||||
.SS inotify events
|
||||
The
|
||||
.BR inotify_add_watch (2)
|
||||
|
|
Loading…
Reference in New Issue