=head1 NAME libev - a high performance full-featured event loop written in C =head1 SYNOPSIS #include =head1 DESCRIPTION Libev is an event loop: you register interest in certain events (such as a file descriptor being readable or a timeout occuring), and it will manage these event sources and provide your program with events. To do this, it must take more or less complete control over your process (or thread) by executing the I handler, and will then communicate events via a callback mechanism. You register interest in certain events by registering so-called I, which are relatively small C structures you initialise with the details of the event, and then hand it over to libev by I the watcher. =head1 FEATURES Libev supports select, poll, the linux-specific epoll and the bsd-specific kqueue mechanisms for file descriptor events, relative timers, absolute timers with customised rescheduling, signal events, process status change events (related to SIGCHLD), and event watchers dealing with the event loop mechanism itself (idle, prepare and check watchers). It also is quite fast (see this L comparing it to libevent for example). =head1 CONVENTIONS Libev is very configurable. In this manual the default configuration will be described, which supports multiple event loops. For more info about various configuration options please have a look at the file F in the libev distribution. If libev was configured without support for multiple event loops, then all functions taking an initial argument of name C (which is always of type C) will not have this argument. =head1 TIME REPRESENTATION Libev represents time as a single floating point number, representing the (fractional) number of seconds since the (POSIX) epoch (somewhere near the beginning of 1970, details are complicated, don't ask). This type is called C, which is what you should use too. It usually aliases to the C type in C, and when you need to do any calculations on it, you should treat it as such. =head1 GLOBAL FUNCTIONS These functions can be called anytime, even before initialising the library in any way. =over 4 =item ev_tstamp ev_time () Returns the current time as libev would use it. Please note that the C function is usually faster and also often returns the timestamp you actually want to know. =item int ev_version_major () =item int ev_version_minor () You can find out the major and minor version numbers of the library you linked against by calling the functions C and C. If you want, you can compare against the global symbols C and C, which specify the version of the library your program was compiled against. Usually, it's a good idea to terminate if the major versions mismatch, as this indicates an incompatible change. Minor versions are usually compatible to older versions, so a larger minor version alone is usually not a problem. Example: make sure we haven't accidentally been linked against the wrong version: assert (("libev version mismatch", ev_version_major () == EV_VERSION_MAJOR && ev_version_minor () >= EV_VERSION_MINOR)); =item unsigned int ev_supported_backends () Return the set of all backends (i.e. their corresponding C value) compiled into this binary of libev (independent of their availability on the system you are running on). See C for a description of the set values. Example: make sure we have the epoll method, because yeah this is cool and a must have and can we have a torrent of it please!!!11 assert (("sorry, no epoll, no sex", ev_supported_backends () & EVBACKEND_EPOLL)); =item unsigned int ev_recommended_backends () Return the set of all backends compiled into this binary of libev and also recommended for this platform. This set is often smaller than the one returned by C, as for example kqueue is broken on most BSDs and will not be autodetected unless you explicitly request it (assuming you know what you are doing). This is the set of backends that libev will probe for if you specify no backends explicitly. =item unsigned int ev_embeddable_backends () Returns the set of backends that are embeddable in other event loops. This is the theoretical, all-platform, value. To find which backends might be supported on the current system, you would need to look at C, likewise for recommended ones. See the description of C watchers for more info. =item ev_set_allocator (void *(*cb)(void *ptr, long size)) Sets the allocation function to use (the prototype is similar to the realloc C function, the semantics are identical). 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. Example: replace the libev allocator with one that waits a bit and then retries: better than mine). static void * persistent_realloc (void *ptr, long size) { for (;;) { void *newptr = realloc (ptr, size); if (newptr) return newptr; sleep (60); } } ... ev_set_allocator (persistent_realloc); =item ev_set_syserr_cb (void (*cb)(const char *msg)); Set the callback function to call on a retryable syscall error (such as failed select, poll, epoll_wait). The message is a printable string indicating the system call or subsystem causing the problem. If this callback is set, then libev will expect it to remedy the sitution, no matter what, when it returns. That is, libev will generally retry the requested operation, or, if the condition doesn't go away, do bad stuff (such as abort). Example: do the same thing as libev does internally: static void fatal_error (const char *msg) { perror (msg); abort (); } ... ev_set_syserr_cb (fatal_error); =back =head1 FUNCTIONS CONTROLLING THE EVENT LOOP An event loop is described by a C. The library knows two types of such loops, the I loop, which supports signals and child events, and dynamically created loops which do not. If you use threads, a common model is to run the default event loop in your main thread (or in a separate thread) and for each thread you create, you also create another event loop. Libev itself does no locking whatsoever, so if you mix calls to the same event loop in different threads, make sure you lock (this is usually a bad idea, though, even if done correctly, because it's hideous and inefficient). =over 4 =item struct ev_loop *ev_default_loop (unsigned int flags) This will initialise the default event loop if it hasn't been initialised yet and return it. If the default loop could not be initialised, returns false. If it already was initialised it simply returns it (and ignores the flags. If that is troubling you, check C afterwards). If you don't know what event loop to use, use the one returned from this function. The flags argument can be used to specify special behaviour or specific backends to use, and is usually specified as C<0> (or C). The following flags are supported: =over 4 =item C The default flags value. Use this if you have no clue (it's the right thing, believe me). =item C If this flag bit is ored into the flag value (or the program runs setuid or setgid) then libev will I look at the environment variable C. Otherwise (the default), this environment variable will 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. =item C (value 1, portable select backend) This is your standard select(2) backend. Not I standard, as libev tries to roll its own fd_set with no limits on the number of fds, but if that fails, expect a fairly low limit on the number of fds when using this backend. It doesn't scale too well (O(highest_fd)), but its usually the fastest backend for a low number of fds. =item C (value 2, poll backend, available everywhere except on windows) And this is your standard poll(2) backend. It's more complicated than select, but handles sparse fds better and has no artificial limit on the number of fds you can use (except it will slow down considerably with a lot of inactive fds). It scales similarly to select, i.e. O(total_fds). =item C (value 4, Linux) For few fds, this backend is a bit little slower than poll and select, but it scales phenomenally better. While poll and select usually scale like O(total_fds) where n is the total number of fds (or the highest fd), epoll scales either O(1) or O(active_fds). While stopping and starting an I/O watcher in the same iteration will result in some caching, there is still a syscall per such incident (because the fd could point to a different file description now), so its best to avoid that. Also, dup()ed file descriptors might not work very well if you register events for both fds. Please note that epoll sometimes generates spurious notifications, so you need to use non-blocking I/O or other means to avoid blocking when no data (or space) is available. =item C (value 8, most BSD clones) Kqueue deserves special mention, as at the time of this writing, it was broken on all BSDs except NetBSD (usually it doesn't work with anything but sockets and pipes, except on Darwin, where of course its completely useless). For this reason its not being "autodetected" unless you explicitly specify it explicitly in the flags (i.e. using C). It scales in the same way as the epoll backend, but the interface to the kernel is more efficient (which says nothing about its actual speed, of course). While starting and stopping an I/O watcher does not cause an extra syscall as with epoll, it still adds up to four event changes per incident, so its best to avoid that. =item C (value 16, Solaris 8) This is not implemented yet (and might never be). =item C (value 32, Solaris 10) This uses the Solaris 10 port mechanism. As with everything on Solaris, it's really slow, but it still scales very well (O(active_fds)). Please note that solaris ports can result in a lot of spurious notifications, so you need to use non-blocking I/O or other means to avoid blocking when no data (or space) is available. =item C Try all backends (even potentially broken ones that wouldn't be tried with C). Since this is a mask, you can do stuff such as C. =back If one or more of these are ored into the flags value, then only these backends will be tried (in the reverse order as given here). If none are specified, most compiled-in backend will be tried, usually in reverse order of their flag values :) The most typical usage is like this: if (!ev_default_loop (0)) fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?"); Restrict libev to the select and poll backends, and do not allow environment settings to be taken into account: ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV); Use whatever libev has to offer, but make sure that kqueue is used if available (warning, breaks stuff, best use only with your own private event loop and only if you know the OS supports your types of fds): ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); =item struct ev_loop *ev_loop_new (unsigned int flags) Similar to C, but always creates a new event loop that is always distinct from the default loop. Unlike the default loop, it cannot handle signal and child watchers, and attempts to do so will be greeted by undefined behaviour (or a failed assertion if assertions are enabled). Example: try to create a event loop that uses epoll and nothing else. struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV); if (!epoller) fatal ("no epoll found here, maybe it hides under your chair"); =item ev_default_destroy () Destroys the default loop again (frees all memory and kernel state etc.). None of the active event watchers will be stopped in the normal sense, so e.g. C might still return true. It is your responsibility to either stop all watchers cleanly yoursef I calling this function, or cope with the fact afterwards (which is usually the easiest thing, youc na just ignore the watchers and/or C them for example). =item ev_loop_destroy (loop) Like C, but destroys an event loop created by an earlier call to C. =item ev_default_fork () This function reinitialises the kernel state for backends that have one. Despite the name, you can call it anytime, but it makes most sense after forking, in either the parent or child process (or both, but that again makes little sense). You I call this function in the child process after forking if and only if you want to use the event library in both processes. If you just fork+exec, you don't have to call it. The function itself is quite fast and it's usually not a problem to call it just in case after a fork. To make this easy, the function will fit in quite nicely into a call to C: pthread_atfork (0, 0, ev_default_fork); At the moment, C and C are safe to use without calling this function, so if you force one of those backends you do not need to care. =item ev_loop_fork (loop) Like C, but acts on an event loop created by C. Yes, you have to call this on every allocated event loop after fork, and how you do this is entirely your own problem. =item unsigned int ev_backend (loop) Returns one of the C flags indicating the event backend in use. =item ev_tstamp ev_now (loop) Returns the current "event loop time", which is the time the event loop received events and started processing them. This timestamp does not change as long as callbacks are being processed, and this is also the base time used for relative timers. You can treat it as the timestamp of the event occuring (or more correctly, libev finding out about it). =item ev_loop (loop, int flags) Finally, this is it, the event handler. This function usually is called after you initialised all your watchers and you want to start handling events. If the flags argument is specified as C<0>, it will not return until either no event watchers are active anymore or C was called. Please note that an explicit C is usually better than relying on all watchers to be stopped when deciding when a program has finished (especially in interactive programs), but having a program that automatically loops as long as it has to and no longer by virtue of relying on its watchers stopping correctly is a thing of beauty. A flags value of C will look for new events, will handle those events and any outstanding ones, but will not block your process in case there are no events and will return after one iteration of the loop. A flags value of C will look for new events (waiting if neccessary) and will handle those and any outstanding ones. It will block your process until at least one new event arrives, and will return after one iteration of the loop. This is useful if you are waiting for some external event in conjunction with something not expressible using other libev watchers. However, a pair of C/C watchers is usually a better approach for this kind of thing. Here are the gory details of what C does: * If there are no active watchers (reference count is zero), return. - Queue prepare watchers and then call all outstanding watchers. - If we have been forked, recreate the kernel state. - Update the kernel state with all outstanding changes. - Update the "event loop time". - Calculate for how long to block. - Block the process, waiting for any events. - Queue all outstanding I/O (fd) events. - Update the "event loop time" and do time jump handling. - Queue all outstanding timers. - Queue all outstanding periodics. - If no events are pending now, queue all idle watchers. - Queue all check watchers. - Call all queued watchers in reverse order (i.e. check watchers first). Signals and child watchers are implemented as I/O watchers, and will be handled here by queueing them when their watcher gets executed. - If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK were used, return, otherwise continue with step *. Example: queue some jobs and then loop until no events are outsanding anymore. ... queue jobs here, make sure they register event watchers as long ... as they still have work to do (even an idle watcher will do..) ev_loop (my_loop, 0); ... jobs done. yeah! =item ev_unloop (loop, how) Can be used to make a call to C return early (but only after it has processed all outstanding events). The C argument must be either C, which will make the innermost C call return, or C, which will make all nested C calls return. =item ev_ref (loop) =item ev_unref (loop) Ref/unref can be used to add or remove a reference count on the event loop: Every watcher keeps one reference, and as long as the reference count is nonzero, C will not return on its own. If you have a watcher you never unregister that should not keep C from returning, ev_unref() after starting, and ev_ref() before stopping it. For example, libev itself uses this for its internal signal pipe: It is not visible to the libev user and should not keep C from exiting if no event watchers registered by it are active. It is also an excellent way to do this for generic recurring timers or from within third-party libraries. Just remember to I and I. Example: create a signal watcher, but keep it from keeping C running when nothing else is active. struct dv_signal exitsig; ev_signal_init (&exitsig, sig_cb, SIGINT); ev_signal_start (myloop, &exitsig); evf_unref (myloop); Example: for some weird reason, unregister the above signal handler again. ev_ref (myloop); ev_signal_stop (myloop, &exitsig); =back =head1 ANATOMY OF A WATCHER A watcher is a structure that you create and register to record your interest in some event. For instance, if you want to wait for STDIN to become readable, you would create an C watcher for that: static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) { ev_io_stop (w); ev_unloop (loop, EVUNLOOP_ALL); } struct ev_loop *loop = ev_default_loop (0); struct ev_io stdin_watcher; ev_init (&stdin_watcher, my_cb); ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ); ev_io_start (loop, &stdin_watcher); ev_loop (loop, 0); As you can see, you are responsible for allocating the memory for your watcher structures (and it is usually a bad idea to do this on the stack, although this can sometimes be quite valid). Each watcher structure must be initialised by a call to C, which expects a callback to be provided. This callback gets invoked each time the event occurs (or, in the case of io watchers, each time the event loop detects that the file descriptor given is readable and/or writable). Each watcher type has its own C<< ev__set (watcher *, ...) >> macro with arguments specific to this watcher type. There is also a macro to combine initialisation and setting in one call: C<< ev__init (watcher *, callback, ...) >>. To make the watcher actually watch out for events, you have to start it with a watcher-specific start function (C<< ev__start (loop, watcher *) >>), and you can stop watching for events at any time by calling the corresponding stop function (C<< ev__stop (loop, watcher *) >>. As long as your watcher is active (has been started but not stopped) you must not touch the values stored in it. Most specifically you must never reinitialise it or call its C macro. Each and every callback receives the event loop pointer as first, the registered watcher structure as second, and a bitset of received events as third argument. The received events usually include a single bit per event type received (you can receive multiple events at the same time). The possible bit masks are: =over 4 =item C =item C The file descriptor in the C watcher has become readable and/or writable. =item C The C watcher has timed out. =item C The C watcher has timed out. =item C The signal specified in the C watcher has been received by a thread. =item C The pid specified in the C watcher has received a status change. =item C The path specified in the C watcher changed its attributes somehow. =item C The C watcher has determined that you have nothing better to do. =item C =item C All C watchers are invoked just I C starts to gather new events, and all C watchers are invoked just after C has gathered them, but before it invokes any callbacks for any received events. Callbacks of both watcher types can start and stop as many watchers as they want, and all of them will be taken into account (for example, a C watcher might start an idle watcher to keep C from blocking). =item C An unspecified error has occured, the watcher has been stopped. This might happen because the watcher could not be properly started because libev ran out of memory, a file descriptor was found to be closed or any other problem. You best act on it by reporting the problem and somehow coping with the watcher being stopped. Libev will usually signal a few "dummy" events together with an error, for example it might indicate that a fd is readable or writable, and if your callbacks is well-written it can just attempt the operation and cope with the error from read() or write(). This will not work in multithreaded programs, though, so beware. =back =head2 GENERIC WATCHER FUNCTIONS In the following description, C stands for the watcher type, e.g. C for C watchers and C for C watchers. =over 4 =item C (ev_TYPE *watcher, callback) This macro initialises the generic portion of a watcher. The contents of the watcher object can be arbitrary (so C will do). Only the generic parts of the watcher are initialised, you I to call the type-specific C macro afterwards to initialise the type-specific parts. For each type there is also a C macro which rolls both calls into one. You can reinitialise a watcher at any time as long as it has been stopped (or never started) and there are no pending events outstanding. The callback is always of type C. =item C (ev_TYPE *, [args]) This macro initialises the type-specific parts of a watcher. You need to call C at least once before you call this macro, but you can call C any number of times. You must not, however, call this macro on a watcher that is active (it can be pending, however, which is a difference to the C macro). Although some watcher types do not have type-specific arguments (e.g. C) you still need to call its C macro. =item C (ev_TYPE *watcher, callback, [args]) This convinience macro rolls both C and C macro calls into a single call. This is the most convinient method to initialise a watcher. The same limitations apply, of course. =item C (loop *, ev_TYPE *watcher) Starts (activates) the given watcher. Only active watchers will receive events. If the watcher is already active nothing will happen. =item C (loop *, ev_TYPE *watcher) Stops the given watcher again (if active) and clears the pending status. It is possible that stopped watchers are pending (for example, non-repeating timers are being stopped when they become pending), but C ensures that the watcher is neither active nor pending. If you want to free or reuse the memory used by the watcher it is therefore a good idea to always call its C function. =item bool ev_is_active (ev_TYPE *watcher) Returns a true value iff the watcher is active (i.e. it has been started and not yet been stopped). As long as a watcher is active you must not modify it. =item bool ev_is_pending (ev_TYPE *watcher) Returns a true value iff the watcher is pending, (i.e. it has outstanding events but its callback has not yet been invoked). As long as a watcher is pending (but not active) you must not call an init function on it (but C is safe) and you must make sure the watcher is available to libev (e.g. you cnanot C it). =item callback = ev_cb (ev_TYPE *watcher) Returns the callback currently set on the watcher. =item ev_cb_set (ev_TYPE *watcher, callback) Change the callback. You can change the callback at virtually any time (modulo threads). =back =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER Each watcher has, by default, a member C that you can change and read at any time, libev will completely ignore it. This can be used to associate arbitrary data with your watcher. If you need more data and don't want to allocate memory and store a pointer to it in that data member, you can also "subclass" the watcher type and provide your own data: struct my_io { struct ev_io io; int otherfd; void *somedata; struct whatever *mostinteresting; } And since your callback will be called with a pointer to the watcher, you can cast it back to your own type: static void my_cb (struct ev_loop *loop, struct ev_io *w_, int revents) { struct my_io *w = (struct my_io *)w_; ... } More interesting and less C-conformant ways of catsing your callback type have been omitted.... =head1 WATCHER TYPES This section describes each watcher in detail, but will not repeat information given in the last section. Any initialisation/set macros, functions and members specific to the watcher type are explained. Members are additionally marked with either I<[read-only]>, meaning that, while the watcher is active, you can look at the member and expect some sensible content, but you must not modify it (you can modify it while the watcher is stopped to your hearts content), or I<[read-write]>, which means you can expect it to have some sensible content while the watcher is active, but you can also modify it. Modifying it may not do something sensible or take immediate effect (or do anything at all), but libev will not crash or malfunction in any way. =head2 C - is this file descriptor readable or writable? I/O watchers check whether a file descriptor is readable or writable in each iteration of the event loop, or, more precisely, when reading would not block the process and writing would at least be able to write some data. This behaviour is called level-triggering because you keep receiving events as long as the condition persists. Remember you can stop the watcher if you don't want to act on the event and neither want to receive future events. In general you can register as many read and/or write event watchers per fd as you want (as long as you don't confuse yourself). Setting all file descriptors to non-blocking mode is also usually a good idea (but not required if you know what you are doing). You have to be careful with dup'ed file descriptors, though. Some backends (the linux epoll backend is a notable example) cannot handle dup'ed file descriptors correctly if you register interest in two or more fds pointing to the same underlying file/socket/etc. description (that is, they share the same underlying "file open"). If you must do this, then force the use of a known-to-be-good backend (at the time of this writing, this includes only C and C). Another thing you have to watch out for is that it is quite easy to receive "spurious" readyness notifications, that is your callback might be called with C but a subsequent C(2) will actually block because there is no data. Not only are some backends known to create a lot of those (for example solaris ports), it is very easy to get into this situation even with a relatively standard program structure. Thus it is best to always use non-blocking I/O: An extra C(2) returning C is far preferable to a program hanging until some data arrives. If you cannot run the fd in non-blocking mode (for example you should not play around with an Xlib connection), then you have to seperately re-test wether a file descriptor is really ready with a known-to-be good interface such as poll (fortunately in our Xlib example, Xlib already does this on its own, so its quite safe to use). =over 4 =item ev_io_init (ev_io *, callback, int fd, int events) =item ev_io_set (ev_io *, int fd, int events) Configures an C watcher. The C is the file descriptor to rceeive events for and events is either C, C or C to receive the given events. =item int fd [read-only] The file descriptor being watched. =item int events [read-only] The events being watched. =back Example: call C when STDIN_FILENO has become, well readable, but only once. Since it is likely line-buffered, you could attempt to read a whole line in the callback: static void stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents) { ev_io_stop (loop, w); .. read from stdin here (or from w->fd) and haqndle any I/O errors } ... struct ev_loop *loop = ev_default_init (0); struct ev_io stdin_readable; ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ); ev_io_start (loop, &stdin_readable); ev_loop (loop, 0); =head2 C - relative and optionally repeating timeouts Timer watchers are simple relative timers that generate an event after a given time, and optionally repeating in regular intervals after that. The timers are based on real time, that is, if you register an event that times out after an hour and you reset your system clock to last years time, it will still time out after (roughly) and hour. "Roughly" because detecting time jumps is hard, and some inaccuracies are unavoidable (the monotonic clock option helps a lot here). The relative timeouts are calculated relative to the C time. This is usually the right thing as this timestamp refers to the time of the event triggering whatever timeout you are modifying/starting. If you suspect event processing to be delayed and you I to base the timeout on the current time, use something like this to adjust for this: ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); 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. =over 4 =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) Configure the timer to trigger after C seconds. If C is C<0.>, then it will automatically be stopped. If it is positive, then the timer will automatically be configured to trigger again C seconds later, again, and again, until stopped manually. The timer itself will do a best-effort at avoiding drift, that is, if you configure a timer to trigger every 10 seconds, then it will trigger at exactly 10 second intervals. If, however, your program cannot keep up with the timer (because it takes longer than those 10 seconds to do stuff) the timer will not fire more than once per event loop iteration. =item ev_timer_again (loop) 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. 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 C with C=C=C<60> and calling C 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 C value and C altogether and only ever use the C value: ev_timer_init (timer, callback, 0., 5.); ev_timer_again (loop, timer); ... timer->again = 17.; ev_timer_again (loop, timer); ... timer->again = 10.; ev_timer_again (loop, timer); This is more efficient then stopping/starting the timer eahc time you want to modify its timeout value. =item ev_tstamp repeat [read-write] The current C value. Will be used each time the watcher times out or C is called and determines the next timeout (if any), which is also when any modifications are taken into account. =back Example: create a timer that fires after 60 seconds. static void one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents) { .. one minute over, w is actually stopped right here } struct ev_timer mytimer; ev_timer_init (&mytimer, one_minute_cb, 60., 0.); ev_timer_start (loop, &mytimer); Example: create a timeout timer that times out after 10 seconds of inactivity. static void timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents) { .. ten seconds without any activity } struct ev_timer mytimer; ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */ ev_timer_again (&mytimer); /* start timer */ ev_loop (loop, 0); // and in some piece of code that gets executed on any "activity": // reset the timeout to start ticking again at 10 seconds ev_timer_again (&mytimer); =head2 C - to cron or not to cron? Periodic watchers are also timers of a kind, but they are very versatile (and unfortunately a bit complex). Unlike C's, they are not based on real time (or relative time) but on wallclock time (absolute time). You can tell a periodic watcher to trigger "at" some specific point in time. For example, if you tell a periodic watcher to trigger in 10 seconds (by specifiying e.g. C) and then reset your system clock to the last year, then it will take a year to trigger the event (unlike an C, which would trigger roughly 10 seconds later and of course not if you reset your system time again). They can also be used to implement vastly more complex timers, such as triggering an event on eahc midnight, local time. As with timers, the callback is guarenteed to be invoked only when the time (C) has been passed, but if multiple periodic timers become ready during the same loop iteration then order of execution is undefined. =over 4 =item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb) =item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb) Lots of arguments, lets sort it out... There are basically three modes of operation, and we will explain them from simplest to complex: =over 4 =item * absolute timer (interval = reschedule_cb = 0) In this configuration the watcher triggers an event at the wallclock time C and doesn't repeat. It will not adjust when a time jump occurs, that is, if it is to be run at January 1st 2011 then it will run when the system time reaches or surpasses this time. =item * non-repeating interval timer (interval > 0, reschedule_cb = 0) In this mode the watcher will always be scheduled to time out at the next C time (for some integer N) and then repeat, regardless of any time jumps. This can be used to create timers that do not drift with respect to system time: ev_periodic_set (&periodic, 0., 3600., 0); This doesn't mean there will always be 3600 seconds in between triggers, but only that the the callback will be called when the system time shows a full hour (UTC), or more correctly, when the system time is evenly divisible by 3600. Another way to think about it (for the mathematically inclined) is that C will try to run the callback in this mode at the next possible time where C