summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2007-11-28 11:27:29 +0000
committerroot <root>2007-11-28 11:27:29 +0000
commit71217f48ea498d7292ca3bf17b8bffe1ab97e642 (patch)
treed086a523b9d7b0922655db81e1e97694cf3d140b /ev.pod
parent4ebe9e295b974622f802229ca8e371ee6df9525a (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod11
1 files changed, 8 insertions, 3 deletions
diff --git a/ev.pod b/ev.pod
index 241fade..8b57eb4 100644
--- a/ev.pod
+++ b/ev.pod
@@ -1224,7 +1224,7 @@ otherwise always forced to be at least one) and all the other fields of
the stat buffer having unspecified contents.
Since there is no standard to do this, the portable implementation simply
-calls C<stat (2)> regulalry on the path to see if it changed somehow. You
+calls C<stat (2)> regularly on the path to see if it changed somehow. You
can specify a recommended polling interval for this case. If you specify
a polling interval of C<0> (highly recommended!) then a I<suitable,
unspecified default> value will be used (which you can expect to be around
@@ -1236,8 +1236,13 @@ This watcher type is not meant for massive numbers of stat watchers,
as even with OS-supported change notifications, this can be
resource-intensive.
-At the time of this writing, no specific OS backends are implemented, but
-if demand increases, at least a kqueue and inotify backend will be added.
+At the time of this writing, only the Linux inotify interface is
+implemented (implementing kqueue support is left as an exercise for the
+reader). Inotify will be used to give hints only and should not change the
+semantics of C<ev_stat> watchers, which means that libev sometimes needs
+to fall back to regular polling again even with inotify, but changes are
+usually detected immediately, and if the file exists there will be no
+polling.
=over 4