| … | |
… | |
| 241 | the current system, you would need to look at C<ev_embeddable_backends () |
241 | the current system, you would need to look at C<ev_embeddable_backends () |
| 242 | & ev_supported_backends ()>, likewise for recommended ones. |
242 | & ev_supported_backends ()>, likewise for recommended ones. |
| 243 | |
243 | |
| 244 | See the description of C<ev_embed> watchers for more info. |
244 | See the description of C<ev_embed> watchers for more info. |
| 245 | |
245 | |
| 246 | =item ev_set_allocator (void *(*cb)(void *ptr, long size)) [NOT REENTRANT] |
246 | =item ev_set_allocator (void *(*cb)(void *ptr, long size)) |
| 247 | |
247 | |
| 248 | Sets the allocation function to use (the prototype is similar - the |
248 | Sets the allocation function to use (the prototype is similar - the |
| 249 | semantics are identical to the C<realloc> C89/SuS/POSIX function). It is |
249 | semantics are identical to the C<realloc> C89/SuS/POSIX function). It is |
| 250 | used to allocate and free memory (no surprises here). If it returns zero |
250 | used to allocate and free memory (no surprises here). If it returns zero |
| 251 | when memory needs to be allocated (C<size != 0>), the library might abort |
251 | when memory needs to be allocated (C<size != 0>), the library might abort |
| … | |
… | |
| 277 | } |
277 | } |
| 278 | |
278 | |
| 279 | ... |
279 | ... |
| 280 | ev_set_allocator (persistent_realloc); |
280 | ev_set_allocator (persistent_realloc); |
| 281 | |
281 | |
| 282 | =item ev_set_syserr_cb (void (*cb)(const char *msg)); [NOT REENTRANT] |
282 | =item ev_set_syserr_cb (void (*cb)(const char *msg)) |
| 283 | |
283 | |
| 284 | Set the callback function to call on a retryable system call error (such |
284 | Set the callback function to call on a retryable system call error (such |
| 285 | as failed select, poll, epoll_wait). The message is a printable string |
285 | as failed select, poll, epoll_wait). The message is a printable string |
| 286 | indicating the system call or subsystem causing the problem. If this |
286 | indicating the system call or subsystem causing the problem. If this |
| 287 | callback is set, then libev will expect it to remedy the situation, no |
287 | callback is set, then libev will expect it to remedy the situation, no |
| … | |
… | |
| 402 | environment variable. |
402 | environment variable. |
| 403 | |
403 | |
| 404 | =item C<EVFLAG_NOINOTIFY> |
404 | =item C<EVFLAG_NOINOTIFY> |
| 405 | |
405 | |
| 406 | When this flag is specified, then libev will not attempt to use the |
406 | When this flag is specified, then libev will not attempt to use the |
| 407 | I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and |
407 | I<inotify> API for its C<ev_stat> watchers. Apart from debugging and |
| 408 | testing, this flag can be useful to conserve inotify file descriptors, as |
408 | testing, this flag can be useful to conserve inotify file descriptors, as |
| 409 | otherwise each loop using C<ev_stat> watchers consumes one inotify handle. |
409 | otherwise each loop using C<ev_stat> watchers consumes one inotify handle. |
| 410 | |
410 | |
| 411 | =item C<EVFLAG_SIGNALFD> |
411 | =item C<EVFLAG_SIGNALFD> |
| 412 | |
412 | |
| 413 | When this flag is specified, then libev will attempt to use the |
413 | When this flag is specified, then libev will attempt to use the |
| 414 | I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API |
414 | I<signalfd> API for its C<ev_signal> (and C<ev_child>) watchers. This API |
| 415 | delivers signals synchronously, which makes it both faster and might make |
415 | delivers signals synchronously, which makes it both faster and might make |
| 416 | it possible to get the queued signal data. It can also simplify signal |
416 | it possible to get the queued signal data. It can also simplify signal |
| 417 | handling with threads, as long as you properly block signals in your |
417 | handling with threads, as long as you properly block signals in your |
| 418 | threads that are not interested in handling them. |
418 | threads that are not interested in handling them. |
| 419 | |
419 | |
| … | |
… | |
| 619 | This function is normally used on loop objects allocated by |
619 | This function is normally used on loop objects allocated by |
| 620 | C<ev_loop_new>, but it can also be used on the default loop returned by |
620 | C<ev_loop_new>, but it can also be used on the default loop returned by |
| 621 | C<ev_default_loop>, in which case it is not thread-safe. |
621 | C<ev_default_loop>, in which case it is not thread-safe. |
| 622 | |
622 | |
| 623 | Note that it is not advisable to call this function on the default loop |
623 | Note that it is not advisable to call this function on the default loop |
| 624 | except in the rare occasion where you really need to free it's resources. |
624 | except in the rare occasion where you really need to free its resources. |
| 625 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
625 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
| 626 | and C<ev_loop_destroy>. |
626 | and C<ev_loop_destroy>. |
| 627 | |
627 | |
| 628 | =item ev_loop_fork (loop) |
628 | =item ev_loop_fork (loop) |
| 629 | |
629 | |
| … | |
… | |
| 2260 | |
2260 | |
| 2261 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2261 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
| 2262 | |
2262 | |
| 2263 | Signal watchers will trigger an event when the process receives a specific |
2263 | Signal watchers will trigger an event when the process receives a specific |
| 2264 | signal one or more times. Even though signals are very asynchronous, libev |
2264 | signal one or more times. Even though signals are very asynchronous, libev |
| 2265 | will try it's best to deliver signals synchronously, i.e. as part of the |
2265 | will try its best to deliver signals synchronously, i.e. as part of the |
| 2266 | normal event processing, like any other event. |
2266 | normal event processing, like any other event. |
| 2267 | |
2267 | |
| 2268 | If you want signals to be delivered truly asynchronously, just use |
2268 | If you want signals to be delivered truly asynchronously, just use |
| 2269 | C<sigaction> as you would do without libev and forget about sharing |
2269 | C<sigaction> as you would do without libev and forget about sharing |
| 2270 | the signal. You can even use C<ev_async> from a signal handler to |
2270 | the signal. You can even use C<ev_async> from a signal handler to |
