From 3360a3869a421bc12a57dcd0a9450ef5ee8a11ec Mon Sep 17 00:00:00 2001
From: root ev_io
- is this file descriptor readable or writable?
+ev_timer
- relative and optionally repeating timeouts
+
+ev_periodic
- to cron or not to cron?
+
+ev_signal
- signal me when a signal gets signalled!
+
+ev_child
- watch out for process status changes
+
+ev_stat
- did the file attributes just change?
+
+ev_idle
- when you've got nothing better to do...
+
+ev_prepare
and ev_check
- customise your event loop!
+
+ev_embed
- when one backend isn't enough...
+
ev_timer
- relative and optionally repeating timeoutsev_periodic
- to cron or not to cron?ev_signal
- signal me when a signal gets signalled!ev_child
- watch out for process status changesev_stat
- did the file attributes just change?ev_idle
- when you've got nothing better to do...ev_prepare
and ev_check
- customise your event loop!ev_embed
- when one backend isn't enough...ev_fork
- the audacity to resume the event loop after a fork
The callback is guarenteed to be invoked only when its timeout has passed, but if multiple timers become ready during the same loop iteration then order of execution is undefined.
+ +As with timers, the callback is guarenteed to be invoked only when the
time (at
) has been passed, but if multiple periodic timers become ready
during the same loop iteration then order of execution is undefined.
SIGxxx
constants).
Child watchers trigger when your process receives a SIGCHLD in response to some child status changes (most typically when a child of yours dies).
+ +ev_stat
watchers, which means that libev sometimes nee
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.
+
+ev_check
watchers are often used to embed other event
loops those other event loops might be in an unusable state until their
ev_check
watcher ran (always remind yourself to coexist peacefully with
others).
+
+