Libev supports select, poll, the linux-specific epoll, the -bsd-specific kqueue and the solaris-specific event port mechanisms -for file descriptor events (ev_io), relative timers (ev_timer), -absolute timers with customised rescheduling (ev_periodic), synchronous -signals (ev_signal), process status change events (ev_child), and -event watchers dealing with the event loop mechanism itself (ev_idle, +

Libev supports select, poll, the Linux-specific epoll, the +BSD-specific kqueue and the Solaris-specific event port mechanisms +for file descriptor events (ev_io), the Linux inotify interface +(for ev_stat), relative timers (ev_timer), absolute timers +with customised rescheduling (ev_periodic), synchronous signals +(ev_signal), process status change events (ev_child), and event +watchers dealing with the event loop mechanism itself (ev_idle, ev_embed, ev_prepare and ev_check watchers) as well as file watchers (ev_stat) and even limited support for fork events (ev_fork).

@@ -231,13 +232,14 @@ might be supported on the current system, you would need to look at recommended ones.

See the description of ev_embed watchers for more info.

ev_set_allocator (void *(*cb)(void *ptr, size_t size))

ev_set_allocator (void *(*cb)(void *ptr, long size))

Sets the allocation function to use (the prototype and semantics are -identical to the realloc C function). It is used to allocate and free -memory (no surprises here). If it returns zero when memory needs to be -allocated, the library might abort or take some potentially destructive -action. The default is your system realloc function.

Sets the allocation function to use (the prototype is similar - the +semantics is identical - to the realloc C function). It is used to +allocate and free memory (no surprises here). If it returns zero when +memory needs to be allocated, the library might abort or take some +potentially destructive action. The default is your system realloc +function.

You could override this function in high-availability programs to, say, free some memory if it cannot allocate memory, to use a special allocator, or even to sleep a while and retry until some memory is available.

@@ -325,6 +327,23 @@ or setgid) then libev will not look at the environment variable override the flags completely if it is found in the environment. This is useful to try out specific backends to test their performance, or to work around bugs.

EVFLAG_FORKCHECK

Instead of calling ev_default_fork or ev_loop_fork manually after +a fork, you can also make libev check for a fork in each iteration by +enabling this flag.

This works by calling getpid () on every iteration of the loop, +and thus this might slow down your event loop if you do a lot of loop +iterations and little real work, but is usually not noticable (on my +Linux system for example, getpid is actually a simple 5-insn sequence +without a syscall and thus very fast, but my Linux system also has +pthread_atfork which is even faster).

The big advantage of this flag is that you can forget about fork (and +forget about forgetting to tell libev about forking) when you use this +flag.

This flag setting cannot be overriden or specified in the LIBEV_FLAGS +environment variable.

EVBACKEND_SELECT (value 1, portable select backend)

@@ -952,20 +971,21 @@ timer will not fire more than once per event loop iteration.

This will act as if the timer timed out and restart it again if it is repeating. The exact semantics are:

If the timer is started but nonrepeating, stop it.

If the timer is repeating, either start it if necessary (with the repeat -value), or reset the running timer to the repeat value.

If the timer is pending, its pending status is cleared.

If the timer is started but nonrepeating, stop it (as if it timed out).

If the timer is repeating, either start it if necessary (with the +repeat value), or reset the running timer to the repeat value.

This sounds a bit complicated, but here is a useful and typical -example: Imagine you have a tcp connection and you want a so-called -idle timeout, that is, you want to be called when there have been, -say, 60 seconds of inactivity on the socket. The easiest way to do -this is to configure an ev_timer with after=repeat=60 and calling +example: Imagine you have a tcp connection and you want a so-called idle +timeout, that is, you want to be called when there have been, say, 60 +seconds of inactivity on the socket. The easiest way to do this is to +configure an ev_timer with a repeat value of 60 and then call ev_timer_again each time you successfully read or write some data. If you go into an idle state where you do not expect data to travel on the -socket, you can stop the timer, and again will automatically restart it if -need be.

You can also ignore the after value and ev_timer_start altogether -and only ever use the repeat value:

+socket, you can ev_timer_stop the timer, and ev_timer_again will +automatically restart it if need be.

That means you can ignore the after value and ev_timer_start +altogether and only ever use the repeat value and ev_timer_again:

   ev_timer_init (timer, callback, 0., 5.);
    ev_timer_again (loop, timer);
    ...
@@ -976,8 +996,8 @@ and only ever use the repeat value:
    ev_timer_again (loop, timer);

This is more efficient then stopping/starting the timer eahc time you want -to modify its timeout value.

This is more slightly efficient then stopping/starting the timer each time +you want to modify its timeout value.

ev_tstamp repeat [read-write]

@@ -1248,8 +1268,10 @@ not exist" is a status change like any other. The condition "path does not exist" is signified by the st_nlink field being zero (which is otherwise always forced to be at least one) and all the other fields of the stat buffer having unspecified contents.

The path should be absolute and must not end in a slash. If it is +relative and your working directory changes, the behaviour is undefined.

Since there is no standard to do this, the portable implementation simply -calls stat (2) regulalry on the path to see if it changed somehow. You +calls 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 0 (highly recommended!) then a suitable, unspecified default value will be used (which you can expect to be around @@ -1259,8 +1281,13 @@ usually overkill.

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 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.

ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)
ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)

Example: Declare and initialise a check watcher, working regardless of -wether multiple loops are supported or not.

Example: Declare and initialise a check watcher, utilising the above +macros so it will work regardless of wether multiple loops are supported +or not.

  static void
   check_cb (EV_P_ ev_timer *w, int revents)
   {
@@ -1827,9 +1855,6 @@ wether multiple loops are supported or not.
   ev_check_start (EV_DEFAULT_ &check);
   ev_loop (EV_DEFAULT_ 0);
 
-
-
-

FEATURES