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.

@@ -1248,6 +1250,8 @@ 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) regularly on the path to see if it changed somehow. You can specify a recommended polling interval for this case. If you specify

FEATURES