… | |
… | |
4 | <head> |
4 | <head> |
5 | <title>libev</title> |
5 | <title>libev</title> |
6 | <meta name="description" content="Pod documentation for libev" /> |
6 | <meta name="description" content="Pod documentation for libev" /> |
7 | <meta name="inputfile" content="<standard input>" /> |
7 | <meta name="inputfile" content="<standard input>" /> |
8 | <meta name="outputfile" content="<standard output>" /> |
8 | <meta name="outputfile" content="<standard output>" /> |
9 | <meta name="created" content="Mon Nov 12 09:11:00 2007" /> |
9 | <meta name="created" content="Mon Nov 12 09:29:10 2007" /> |
10 | <meta name="generator" content="Pod::Xhtml 1.57" /> |
10 | <meta name="generator" content="Pod::Xhtml 1.57" /> |
11 | <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> |
11 | <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> |
12 | <body> |
12 | <body> |
13 | <div class="pod"> |
13 | <div class="pod"> |
14 | <!-- INDEX START --> |
14 | <!-- INDEX START --> |
… | |
… | |
71 | <div id="FEATURES_CONTENT"> |
71 | <div id="FEATURES_CONTENT"> |
72 | <p>Libev supports select, poll, the linux-specific epoll and the bsd-specific |
72 | <p>Libev supports select, poll, the linux-specific epoll and the bsd-specific |
73 | kqueue mechanisms for file descriptor events, relative timers, absolute |
73 | kqueue mechanisms for file descriptor events, relative timers, absolute |
74 | timers with customised rescheduling, signal events, process status change |
74 | timers with customised rescheduling, signal events, process status change |
75 | events (related to SIGCHLD), and event watchers dealing with the event |
75 | events (related to SIGCHLD), and event watchers dealing with the event |
76 | loop mechanism itself (idle, prepare and check watchers).</p> |
76 | loop mechanism itself (idle, prepare and check watchers). It also is quite |
|
|
77 | fast (see this <a href="http://libev.schmorp.de/bench.html">benchmark</a> comparing |
|
|
78 | it to libevent for example).</p> |
77 | |
79 | |
78 | </div> |
80 | </div> |
79 | <h1 id="CONVENTIONS">CONVENTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> |
81 | <h1 id="CONVENTIONS">CONVENTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> |
80 | <div id="CONVENTIONS_CONTENT"> |
82 | <div id="CONVENTIONS_CONTENT"> |
81 | <p>Libev is very configurable. In this manual the default configuration |
83 | <p>Libev is very configurable. In this manual the default configuration |
82 | will be described, which supports multiple event loops. For more info |
84 | will be described, which supports multiple event loops. For more info |
83 | about various configuraiton options please have a look at the file |
85 | about various configuration options please have a look at the file |
84 | <cite>README.embed</cite> in the libev distribution. If libev was configured without |
86 | <cite>README.embed</cite> in the libev distribution. If libev was configured without |
85 | support for multiple event loops, then all functions taking an initial |
87 | support for multiple event loops, then all functions taking an initial |
86 | argument of name <code>loop</code> (which is always of type <code>struct ev_loop *</code>) |
88 | argument of name <code>loop</code> (which is always of type <code>struct ev_loop *</code>) |
87 | will not have this argument.</p> |
89 | will not have this argument.</p> |
88 | |
90 | |
… | |
… | |
105 | <p>You can find out the major and minor version numbers of the library |
107 | <p>You can find out the major and minor version numbers of the library |
106 | you linked against by calling the functions <code>ev_version_major</code> and |
108 | you linked against by calling the functions <code>ev_version_major</code> and |
107 | <code>ev_version_minor</code>. If you want, you can compare against the global |
109 | <code>ev_version_minor</code>. If you want, you can compare against the global |
108 | symbols <code>EV_VERSION_MAJOR</code> and <code>EV_VERSION_MINOR</code>, which specify the |
110 | symbols <code>EV_VERSION_MAJOR</code> and <code>EV_VERSION_MINOR</code>, which specify the |
109 | version of the library your program was compiled against.</p> |
111 | version of the library your program was compiled against.</p> |
110 | <p>Usually, its a good idea to terminate if the major versions mismatch, |
112 | <p>Usually, it's a good idea to terminate if the major versions mismatch, |
111 | as this indicates an incompatible change. Minor versions are usually |
113 | as this indicates an incompatible change. Minor versions are usually |
112 | compatible to older versions, so a larger minor version alone is usually |
114 | compatible to older versions, so a larger minor version alone is usually |
113 | not a problem.</p> |
115 | not a problem.</p> |
114 | </dd> |
116 | </dd> |
115 | <dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt> |
117 | <dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt> |
116 | <dd> |
118 | <dd> |
117 | <p>Sets the allocation function to use (the prototype is similar to the |
119 | <p>Sets the allocation function to use (the prototype is similar to the |
118 | realloc function). It is used to allocate and free memory (no surprises |
120 | realloc C function, the semantics are identical). It is used to allocate |
119 | here). If it returns zero when memory needs to be allocated, the library |
121 | and free memory (no surprises here). If it returns zero when memory |
120 | might abort or take some potentially destructive action. The default is |
122 | needs to be allocated, the library might abort or take some potentially |
121 | your system realloc function.</p> |
123 | destructive action. The default is your system realloc function.</p> |
122 | <p>You could override this function in high-availability programs to, say, |
124 | <p>You could override this function in high-availability programs to, say, |
123 | free some memory if it cannot allocate memory, to use a special allocator, |
125 | free some memory if it cannot allocate memory, to use a special allocator, |
124 | or even to sleep a while and retry until some memory is available.</p> |
126 | or even to sleep a while and retry until some memory is available.</p> |
125 | </dd> |
127 | </dd> |
126 | <dt>ev_set_syserr_cb (void (*cb)(const char *msg));</dt> |
128 | <dt>ev_set_syserr_cb (void (*cb)(const char *msg));</dt> |
127 | <dd> |
129 | <dd> |
128 | <p>Set the callback function to call on a retryable syscall error (such |
130 | <p>Set the callback function to call on a retryable syscall error (such |
129 | as failed select, poll, epoll_wait). The message is a printable string |
131 | as failed select, poll, epoll_wait). The message is a printable string |
130 | indicating the system call or subsystem causing the problem. If this |
132 | indicating the system call or subsystem causing the problem. If this |
131 | callback is set, then libev will expect it to remedy the sitution, no |
133 | callback is set, then libev will expect it to remedy the sitution, no |
132 | matter what, when it returns. That is, libev will geenrally retry the |
134 | matter what, when it returns. That is, libev will generally retry the |
133 | requested operation, or, if the condition doesn't go away, do bad stuff |
135 | requested operation, or, if the condition doesn't go away, do bad stuff |
134 | (such as abort).</p> |
136 | (such as abort).</p> |
135 | </dd> |
137 | </dd> |
136 | </dl> |
138 | </dl> |
137 | |
139 | |
… | |
… | |
141 | <p>An event loop is described by a <code>struct ev_loop *</code>. The library knows two |
143 | <p>An event loop is described by a <code>struct ev_loop *</code>. The library knows two |
142 | types of such loops, the <i>default</i> loop, which supports signals and child |
144 | types of such loops, the <i>default</i> loop, which supports signals and child |
143 | events, and dynamically created loops which do not.</p> |
145 | events, and dynamically created loops which do not.</p> |
144 | <p>If you use threads, a common model is to run the default event loop |
146 | <p>If you use threads, a common model is to run the default event loop |
145 | in your main thread (or in a separate thrad) and for each thread you |
147 | in your main thread (or in a separate thrad) and for each thread you |
146 | create, you also create another event loop. Libev itself does no lockign |
148 | create, you also create another event loop. Libev itself does no locking |
147 | whatsoever, so if you mix calls to different event loops, make sure you |
149 | whatsoever, so if you mix calls to the same event loop in different |
148 | lock (this is usually a bad idea, though, even if done right).</p> |
150 | threads, make sure you lock (this is usually a bad idea, though, even if |
|
|
151 | done correctly, because it's hideous and inefficient).</p> |
149 | <dl> |
152 | <dl> |
150 | <dt>struct ev_loop *ev_default_loop (unsigned int flags)</dt> |
153 | <dt>struct ev_loop *ev_default_loop (unsigned int flags)</dt> |
151 | <dd> |
154 | <dd> |
152 | <p>This will initialise the default event loop if it hasn't been initialised |
155 | <p>This will initialise the default event loop if it hasn't been initialised |
153 | yet and return it. If the default loop could not be initialised, returns |
156 | yet and return it. If the default loop could not be initialised, returns |
154 | false. If it already was initialised it simply returns it (and ignores the |
157 | false. If it already was initialised it simply returns it (and ignores the |
155 | flags).</p> |
158 | flags).</p> |
156 | <p>If you don't know what event loop to use, use the one returned from this |
159 | <p>If you don't know what event loop to use, use the one returned from this |
157 | function.</p> |
160 | function.</p> |
158 | <p>The flags argument can be used to specify special behaviour or specific |
161 | <p>The flags argument can be used to specify special behaviour or specific |
159 | backends to use, and is usually specified as 0 (or EVFLAG_AUTO)</p> |
162 | backends to use, and is usually specified as 0 (or EVFLAG_AUTO).</p> |
160 | <p>It supports the following flags:</p> |
163 | <p>It supports the following flags:</p> |
161 | <p> |
164 | <p> |
162 | <dl> |
165 | <dl> |
163 | <dt>EVFLAG_AUTO</dt> |
166 | <dt>EVFLAG_AUTO</dt> |
164 | <dd> |
167 | <dd> |
165 | <p>The default flags value. Use this if you have no clue (its the right |
168 | <p>The default flags value. Use this if you have no clue (it's the right |
166 | thing, believe me).</p> |
169 | thing, believe me).</p> |
167 | </dd> |
170 | </dd> |
168 | <dt>EVFLAG_NOENV</dt> |
171 | <dt>EVFLAG_NOENV</dt> |
169 | <dd> |
172 | <dd> |
170 | <p>If this flag bit is ored into the flag value then libev will <i>not</i> look |
173 | <p>If this flag bit is ored into the flag value (or the program runs setuid |
171 | at the environment variable <code>LIBEV_FLAGS</code>. Otherwise (the default), this |
174 | or setgid) then libev will <i>not</i> look at the environment variable |
172 | environment variable will override the flags completely. This is useful |
175 | <code>LIBEV_FLAGS</code>. Otherwise (the default), this environment variable will |
|
|
176 | override the flags completely if it is found in the environment. This is |
173 | to try out specific backends to tets their performance, or to work around |
177 | useful to try out specific backends to test their performance, or to work |
174 | bugs.</p> |
178 | around bugs.</p> |
175 | </dd> |
179 | </dd> |
176 | <dt>EVMETHOD_SELECT portable select backend</dt> |
180 | <dt>EVMETHOD_SELECT (portable select backend)</dt> |
177 | <dt>EVMETHOD_POLL poll backend (everywhere except windows)</dt> |
181 | <dt>EVMETHOD_POLL (poll backend, available everywhere except on windows)</dt> |
178 | <dt>EVMETHOD_EPOLL linux only</dt> |
182 | <dt>EVMETHOD_EPOLL (linux only)</dt> |
179 | <dt>EVMETHOD_KQUEUE some bsds only</dt> |
183 | <dt>EVMETHOD_KQUEUE (some bsds only)</dt> |
180 | <dt>EVMETHOD_DEVPOLL solaris 8 only</dt> |
184 | <dt>EVMETHOD_DEVPOLL (solaris 8 only)</dt> |
181 | <dt>EVMETHOD_PORT solaris 10 only</dt> |
185 | <dt>EVMETHOD_PORT (solaris 10 only)</dt> |
182 | <dd> |
186 | <dd> |
183 | <p>If one or more of these are ored into the flags value, then only these |
187 | <p>If one or more of these are ored into the flags value, then only these |
184 | backends will be tried (in the reverse order as given here). If one are |
188 | backends will be tried (in the reverse order as given here). If one are |
185 | specified, any backend will do.</p> |
189 | specified, any backend will do.</p> |
186 | </dd> |
190 | </dd> |
… | |
… | |
196 | </dd> |
200 | </dd> |
197 | <dt>ev_default_destroy ()</dt> |
201 | <dt>ev_default_destroy ()</dt> |
198 | <dd> |
202 | <dd> |
199 | <p>Destroys the default loop again (frees all memory and kernel state |
203 | <p>Destroys the default loop again (frees all memory and kernel state |
200 | etc.). This stops all registered event watchers (by not touching them in |
204 | etc.). This stops all registered event watchers (by not touching them in |
201 | any way whatsoever, although you cnanot rely on this :).</p> |
205 | any way whatsoever, although you cannot rely on this :).</p> |
202 | </dd> |
206 | </dd> |
203 | <dt>ev_loop_destroy (loop)</dt> |
207 | <dt>ev_loop_destroy (loop)</dt> |
204 | <dd> |
208 | <dd> |
205 | <p>Like <code>ev_default_destroy</code>, but destroys an event loop created by an |
209 | <p>Like <code>ev_default_destroy</code>, but destroys an event loop created by an |
206 | earlier call to <code>ev_loop_new</code>.</p> |
210 | earlier call to <code>ev_loop_new</code>.</p> |
… | |
… | |
212 | after forking, in either the parent or child process (or both, but that |
216 | after forking, in either the parent or child process (or both, but that |
213 | again makes little sense).</p> |
217 | again makes little sense).</p> |
214 | <p>You <i>must</i> call this function after forking if and only if you want to |
218 | <p>You <i>must</i> call this function after forking if and only if you want to |
215 | use the event library in both processes. If you just fork+exec, you don't |
219 | use the event library in both processes. If you just fork+exec, you don't |
216 | have to call it.</p> |
220 | have to call it.</p> |
217 | <p>The function itself is quite fast and its usually not a problem to call |
221 | <p>The function itself is quite fast and it's usually not a problem to call |
218 | it just in case after a fork. To make this easy, the function will fit in |
222 | it just in case after a fork. To make this easy, the function will fit in |
219 | quite nicely into a call to <code>pthread_atfork</code>:</p> |
223 | quite nicely into a call to <code>pthread_atfork</code>:</p> |
220 | <pre> pthread_atfork (0, 0, ev_default_fork); |
224 | <pre> pthread_atfork (0, 0, ev_default_fork); |
221 | |
225 | |
222 | </pre> |
226 | </pre> |
… | |
… | |
230 | <dt>unsigned int ev_method (loop)</dt> |
234 | <dt>unsigned int ev_method (loop)</dt> |
231 | <dd> |
235 | <dd> |
232 | <p>Returns one of the <code>EVMETHOD_*</code> flags indicating the event backend in |
236 | <p>Returns one of the <code>EVMETHOD_*</code> flags indicating the event backend in |
233 | use.</p> |
237 | use.</p> |
234 | </dd> |
238 | </dd> |
235 | <dt>ev_tstamp = ev_now (loop)</dt> |
239 | <dt>ev_tstamp ev_now (loop)</dt> |
236 | <dd> |
240 | <dd> |
237 | <p>Returns the current "event loop time", which is the time the event loop |
241 | <p>Returns the current "event loop time", which is the time the event loop |
238 | got events and started processing them. This timestamp does not change |
242 | got events and started processing them. This timestamp does not change |
239 | as long as callbacks are being processed, and this is also the base time |
243 | as long as callbacks are being processed, and this is also the base time |
240 | used for relative timers. You can treat it as the timestamp of the event |
244 | used for relative timers. You can treat it as the timestamp of the event |
… | |
… | |
247 | events.</p> |
251 | events.</p> |
248 | <p>If the flags argument is specified as 0, it will not return until either |
252 | <p>If the flags argument is specified as 0, it will not return until either |
249 | no event watchers are active anymore or <code>ev_unloop</code> was called.</p> |
253 | no event watchers are active anymore or <code>ev_unloop</code> was called.</p> |
250 | <p>A flags value of <code>EVLOOP_NONBLOCK</code> will look for new events, will handle |
254 | <p>A flags value of <code>EVLOOP_NONBLOCK</code> will look for new events, will handle |
251 | those events and any outstanding ones, but will not block your process in |
255 | those events and any outstanding ones, but will not block your process in |
252 | case there are no events.</p> |
256 | case there are no events and will return after one iteration of the loop.</p> |
253 | <p>A flags value of <code>EVLOOP_ONESHOT</code> will look for new events (waiting if |
257 | <p>A flags value of <code>EVLOOP_ONESHOT</code> will look for new events (waiting if |
254 | neccessary) and will handle those and any outstanding ones. It will block |
258 | neccessary) and will handle those and any outstanding ones. It will block |
255 | your process until at least one new event arrives.</p> |
259 | your process until at least one new event arrives, and will return after |
|
|
260 | one iteration of the loop.</p> |
256 | <p>This flags value could be used to implement alternative looping |
261 | <p>This flags value could be used to implement alternative looping |
257 | constructs, but the <code>prepare</code> and <code>check</code> watchers provide a better and |
262 | constructs, but the <code>prepare</code> and <code>check</code> watchers provide a better and |
258 | more generic mechanism.</p> |
263 | more generic mechanism.</p> |
259 | </dd> |
264 | </dd> |
260 | <dt>ev_unloop (loop, how)</dt> |
265 | <dt>ev_unloop (loop, how)</dt> |
261 | <dd> |
266 | <dd> |
262 | <p>Can be used to make a call to <code>ev_loop</code> return early. The <code>how</code> argument |
267 | <p>Can be used to make a call to <code>ev_loop</code> return early (but only after it |
|
|
268 | has processed all outstanding events). The <code>how</code> argument must be either |
263 | must be either <code>EVUNLOOP_ONCE</code>, which will make the innermost <code>ev_loop</code> |
269 | <code>EVUNLOOP_ONCE</code>, which will make the innermost <code>ev_loop</code> call return, or |
264 | call return, or <code>EVUNLOOP_ALL</code>, which will make all nested <code>ev_loop</code> |
270 | <code>EVUNLOOP_ALL</code>, which will make all nested <code>ev_loop</code> calls return.</p> |
265 | calls return.</p> |
|
|
266 | </dd> |
271 | </dd> |
267 | <dt>ev_ref (loop)</dt> |
272 | <dt>ev_ref (loop)</dt> |
268 | <dt>ev_unref (loop)</dt> |
273 | <dt>ev_unref (loop)</dt> |
269 | <dd> |
274 | <dd> |
270 | <p>Ref/unref can be used to add or remove a refcount on the event loop: Every |
275 | <p>Ref/unref can be used to add or remove a reference count on the event |
271 | watcher keeps one reference. If you have a long-runing watcher you never |
276 | loop: Every watcher keeps one reference, and as long as the reference |
272 | unregister that should not keep ev_loop from running, ev_unref() after |
277 | count is nonzero, <code>ev_loop</code> will not return on its own. If you have |
273 | starting, and ev_ref() before stopping it. Libev itself uses this for |
278 | a watcher you never unregister that should not keep <code>ev_loop</code> from |
274 | example for its internal signal pipe: It is not visible to you as a user |
279 | returning, ev_unref() after starting, and ev_ref() before stopping it. For |
275 | and should not keep <code>ev_loop</code> from exiting if the work is done. It is |
280 | example, libev itself uses this for its internal signal pipe: It is not |
276 | also an excellent way to do this for generic recurring timers or from |
281 | visible to the libev user and should not keep <code>ev_loop</code> from exiting if |
277 | within third-party libraries. Just remember to unref after start and ref |
282 | no event watchers registered by it are active. It is also an excellent |
278 | before stop.</p> |
283 | way to do this for generic recurring timers or from within third-party |
|
|
284 | libraries. Just remember to <i>unref after start</i> and <i>ref before stop</i>.</p> |
279 | </dd> |
285 | </dd> |
280 | </dl> |
286 | </dl> |
281 | |
287 | |
282 | </div> |
288 | </div> |
283 | <h1 id="ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</h1><p><a href="#TOP" class="toplink">Top</a></p> |
289 | <h1 id="ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</h1><p><a href="#TOP" class="toplink">Top</a></p> |
… | |
… | |
427 | <p>I/O watchers check whether a file descriptor is readable or writable |
433 | <p>I/O watchers check whether a file descriptor is readable or writable |
428 | in each iteration of the event loop (This behaviour is called |
434 | in each iteration of the event loop (This behaviour is called |
429 | level-triggering because you keep receiving events as long as the |
435 | level-triggering because you keep receiving events as long as the |
430 | condition persists. Remember you cna stop the watcher if you don't want to |
436 | condition persists. Remember you cna stop the watcher if you don't want to |
431 | act on the event and neither want to receive future events).</p> |
437 | act on the event and neither want to receive future events).</p> |
|
|
438 | <p>In general you can register as many read and/or write event watchers oer |
|
|
439 | fd as you want (as long as you don't confuse yourself). Setting all file |
|
|
440 | descriptors to non-blocking mode is also usually a good idea (but not |
|
|
441 | required if you know what you are doing).</p> |
|
|
442 | <p>You have to be careful with dup'ed file descriptors, though. Some backends |
|
|
443 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
|
|
444 | descriptors correctly if you register interest in two or more fds pointing |
|
|
445 | to the same file/socket etc. description.</p> |
|
|
446 | <p>If you must do this, then force the use of a known-to-be-good backend |
|
|
447 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
|
|
448 | EVMETHOD_POLL).</p> |
432 | <dl> |
449 | <dl> |
433 | <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> |
450 | <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> |
434 | <dt>ev_io_set (ev_io *, int fd, int events)</dt> |
451 | <dt>ev_io_set (ev_io *, int fd, int events)</dt> |
435 | <dd> |
452 | <dd> |
436 | <p>Configures an ev_io watcher. The fd is the file descriptor to rceeive |
453 | <p>Configures an ev_io watcher. The fd is the file descriptor to rceeive |
… | |
… | |
447 | <p>The timers are based on real time, that is, if you register an event that |
464 | <p>The timers are based on real time, that is, if you register an event that |
448 | times out after an hour and youreset your system clock to last years |
465 | times out after an hour and youreset your system clock to last years |
449 | time, it will still time out after (roughly) and hour. "Roughly" because |
466 | time, it will still time out after (roughly) and hour. "Roughly" because |
450 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
467 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
451 | monotonic clock option helps a lot here).</p> |
468 | monotonic clock option helps a lot here).</p> |
|
|
469 | <p>The relative timeouts are calculated relative to the <code>ev_now ()</code> |
|
|
470 | time. This is usually the right thing as this timestamp refers to the time |
|
|
471 | of the event triggering whatever timeout you are modifying/starting. If |
|
|
472 | you suspect event processing to be delayed and you *need* to base the timeout |
|
|
473 | ion the current time, use something like this to adjust for this:</p> |
|
|
474 | <pre> ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
|
|
475 | |
|
|
476 | </pre> |
452 | <dl> |
477 | <dl> |
453 | <dt>ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)</dt> |
478 | <dt>ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)</dt> |
454 | <dt>ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)</dt> |
479 | <dt>ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)</dt> |
455 | <dd> |
480 | <dd> |
456 | <p>Configure the timer to trigger after <code>after</code> seconds. If <code>repeat</code> is |
481 | <p>Configure the timer to trigger after <code>after</code> seconds. If <code>repeat</code> is |
… | |
… | |
574 | </div> |
599 | </div> |
575 | <h2 id="ev_signal_signal_me_when_a_signal_ge">ev_signal - signal me when a signal gets signalled</h2> |
600 | <h2 id="ev_signal_signal_me_when_a_signal_ge">ev_signal - signal me when a signal gets signalled</h2> |
576 | <div id="ev_signal_signal_me_when_a_signal_ge-2"> |
601 | <div id="ev_signal_signal_me_when_a_signal_ge-2"> |
577 | <p>Signal watchers will trigger an event when the process receives a specific |
602 | <p>Signal watchers will trigger an event when the process receives a specific |
578 | signal one or more times. Even though signals are very asynchronous, libev |
603 | signal one or more times. Even though signals are very asynchronous, libev |
579 | will try its best to deliver signals synchronously, i.e. as part of the |
604 | will try it's best to deliver signals synchronously, i.e. as part of the |
580 | normal event processing, like any other event.</p> |
605 | normal event processing, like any other event.</p> |
581 | <p>You cna configure as many watchers as you like per signal. Only when the |
606 | <p>You cna configure as many watchers as you like per signal. Only when the |
582 | first watcher gets started will libev actually register a signal watcher |
607 | first watcher gets started will libev actually register a signal watcher |
583 | with the kernel (thus it coexists with your own signal handlers as long |
608 | with the kernel (thus it coexists with your own signal handlers as long |
584 | as you don't register any with libev). Similarly, when the last signal |
609 | as you don't register any with libev). Similarly, when the last signal |