… | |
… | |
37 | # CHILD/PID STATUS CHANGES |
37 | # CHILD/PID STATUS CHANGES |
38 | |
38 | |
39 | my $w = EV::child 666, sub { |
39 | my $w = EV::child 666, sub { |
40 | my ($w, $revents) = @_; |
40 | my ($w, $revents) = @_; |
41 | my $status = $w->rstatus; |
41 | my $status = $w->rstatus; |
|
|
42 | }; |
|
|
43 | |
|
|
44 | # STAT CHANGES |
|
|
45 | my $w = EV::stat "/etc/passwd", 10, sub { |
|
|
46 | my ($w, $revents) = @_; |
|
|
47 | warn $w->path, " has changed somehow.\n"; |
42 | }; |
48 | }; |
43 | |
49 | |
44 | # MAINLOOP |
50 | # MAINLOOP |
45 | EV::loop; # loop until EV::unloop is called or all watchers stop |
51 | EV::loop; # loop until EV::unloop is called or all watchers stop |
46 | EV::loop EV::LOOP_ONESHOT; # block until at least one event could be handled |
52 | EV::loop EV::LOOP_ONESHOT; # block until at least one event could be handled |
47 | EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block |
53 | EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block |
48 | |
54 | |
49 | DESCRIPTION |
55 | DESCRIPTION |
50 | This module provides an interface to libev |
56 | This module provides an interface to libev |
51 | (<http://software.schmorp.de/pkg/libev.html>). |
57 | (<http://software.schmorp.de/pkg/libev.html>). While the documentation |
|
|
58 | below is comprehensive, one might also consult the documentation of |
|
|
59 | libev itself (<http://cvs.schmorp.de/libev/ev.html>) for more subtle |
|
|
60 | details on watcher semantics or some discussion on the available |
|
|
61 | backends, or how to force a specific backend with "LIBEV_FLAGS". |
52 | |
62 | |
53 | BASIC INTERFACE |
63 | BASIC INTERFACE |
54 | $EV::DIED |
64 | $EV::DIED |
55 | Must contain a reference to a function that is called when a |
65 | Must contain a reference to a function that is called when a |
56 | callback throws an exception (with $@ containing thr error). The |
66 | callback throws an exception (with $@ containing thr error). The |
… | |
… | |
85 | makes the innermost call to EV::loop return. |
95 | makes the innermost call to EV::loop return. |
86 | |
96 | |
87 | When called with an argument of EV::UNLOOP_ALL, all calls to |
97 | When called with an argument of EV::UNLOOP_ALL, all calls to |
88 | EV::loop will return as fast as possible. |
98 | EV::loop will return as fast as possible. |
89 | |
99 | |
90 | WATCHER |
100 | EV::once $fh_or_undef, $events, $timeout, $cb->($revents) |
|
|
101 | This function rolls together an I/O and a timer watcher for a single |
|
|
102 | one-shot event without the need for managing a watcher object. |
|
|
103 | |
|
|
104 | If $fh_or_undef is a filehandle or file descriptor, then $events |
|
|
105 | must be a bitset containing either "EV::READ", "EV::WRITE" or |
|
|
106 | "EV::READ | EV::WRITE", indicating the type of I/O event you want to |
|
|
107 | wait for. If you do not want to wait for some I/O event, specify |
|
|
108 | "undef" for $fh_or_undef and 0 for $events). |
|
|
109 | |
|
|
110 | If timeout is "undef" or negative, then there will be no timeout. |
|
|
111 | Otherwise a EV::timer with this value will be started. |
|
|
112 | |
|
|
113 | When an error occurs or either the timeout or I/O watcher triggers, |
|
|
114 | then the callback will be called with the received event set (in |
|
|
115 | general you can expect it to be a combination of "EV:ERROR", |
|
|
116 | "EV::READ", "EV::WRITE" and "EV::TIMEOUT"). |
|
|
117 | |
|
|
118 | EV::once doesn't return anything: the watchers stay active till |
|
|
119 | either of them triggers, then they will be stopped and freed, and |
|
|
120 | the callback invoked. |
|
|
121 | |
|
|
122 | WATCHER OBJECTS |
91 | A watcher is an object that gets created to record your interest in some |
123 | A watcher is an object that gets created to record your interest in some |
92 | event. For instance, if you want to wait for STDIN to become readable, |
124 | event. For instance, if you want to wait for STDIN to become readable, |
93 | you would create an EV::io watcher for that: |
125 | you would create an EV::io watcher for that: |
94 | |
126 | |
95 | my $watcher = EV::io *STDIN, EV::READ, sub { |
127 | my $watcher = EV::io *STDIN, EV::READ, sub { |
… | |
… | |
119 | |
151 | |
120 | Also, all methods changing some aspect of a watcher (->set, ->priority, |
152 | Also, all methods changing some aspect of a watcher (->set, ->priority, |
121 | ->fh and so on) automatically stop and start it again if it is active, |
153 | ->fh and so on) automatically stop and start it again if it is active, |
122 | which means pending events get lost. |
154 | which means pending events get lost. |
123 | |
155 | |
124 | WATCHER TYPES |
156 | COMMON WATCHER METHODS |
125 | Now lets move to the existing watcher types and asociated methods. |
157 | This section lists methods common to all watchers. |
126 | |
|
|
127 | The following methods are available for all watchers. Then followes a |
|
|
128 | description of each watcher constructor (EV::io, EV::timer, |
|
|
129 | EV::periodic, EV::signal, EV::child, EV::idle, EV::prepare and |
|
|
130 | EV::check), followed by any type-specific methods (if any). |
|
|
131 | |
158 | |
132 | $w->start |
159 | $w->start |
133 | Starts a watcher if it isn't active already. Does nothing to an |
160 | Starts a watcher if it isn't active already. Does nothing to an |
134 | already active watcher. By default, all watchers start out in the |
161 | already active watcher. By default, all watchers start out in the |
135 | active state (see the description of the "_ns" variants if you need |
162 | active state (see the description of the "_ns" variants if you need |
… | |
… | |
165 | Pending watchers with higher priority will be invoked first. The |
192 | Pending watchers with higher priority will be invoked first. The |
166 | valid range of priorities lies between EV::MAXPRI (default 2) and |
193 | valid range of priorities lies between EV::MAXPRI (default 2) and |
167 | EV::MINPRI (default -2). If the priority is outside this range it |
194 | EV::MINPRI (default -2). If the priority is outside this range it |
168 | will automatically be normalised to the nearest valid priority. |
195 | will automatically be normalised to the nearest valid priority. |
169 | |
196 | |
170 | The default priority of any newly-created weatcher is 0. |
197 | The default priority of any newly-created watcher is 0. |
|
|
198 | |
|
|
199 | Note that the priority semantics have not yet been fleshed out and |
|
|
200 | are subject to almost certain change. |
171 | |
201 | |
172 | $w->trigger ($revents) |
202 | $w->trigger ($revents) |
173 | Call the callback *now* with the given event mask. |
203 | Call the callback *now* with the given event mask. |
174 | |
204 | |
|
|
205 | $previous_state = $w->keepalive ($bool) |
|
|
206 | Normally, "EV::loop" will return when there are no active watchers |
|
|
207 | (which is a "deadlock" because no progress can be made anymore). |
|
|
208 | This is convinient because it allows you to start your watchers (and |
|
|
209 | your jobs), call "EV::loop" once and when it returns you know that |
|
|
210 | all your jobs are finished (or they forgot to register some watchers |
|
|
211 | for their task :). |
|
|
212 | |
|
|
213 | Sometimes, however, this gets in your way, for example when you the |
|
|
214 | module that calls "EV::loop" (usually the main program) is not the |
|
|
215 | same module as a long-living watcher (for example a DNS client |
|
|
216 | module written by somebody else even). Then you might want any |
|
|
217 | outstanding requests to be handled, but you would not want to keep |
|
|
218 | "EV::loop" from returning just because you happen to have this |
|
|
219 | long-running UDP port watcher. |
|
|
220 | |
|
|
221 | In this case you can clear the keepalive status, which means that |
|
|
222 | even though your watcher is active, it won't keep "EV::loop" from |
|
|
223 | returning. |
|
|
224 | |
|
|
225 | The initial value for keepalive is true (enabled), and you cna |
|
|
226 | change it any time. |
|
|
227 | |
|
|
228 | Example: Register an IO watcher for some UDP socket but do not keep |
|
|
229 | the event loop from running just because of that watcher. |
|
|
230 | |
|
|
231 | my $udp_socket = ... |
|
|
232 | my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... }; |
|
|
233 | $udp_watcher->keepalive (0); |
|
|
234 | |
|
|
235 | WATCHER TYPES |
|
|
236 | Each of the following subsections describes a single watcher type. |
|
|
237 | |
|
|
238 | IO WATCHERS - is this file descriptor readable or writable? |
175 | $w = EV::io $fileno_or_fh, $eventmask, $callback |
239 | $w = EV::io $fileno_or_fh, $eventmask, $callback |
176 | $w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
240 | $w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
177 | As long as the returned watcher object is alive, call the $callback |
241 | As long as the returned watcher object is alive, call the $callback |
178 | when the events specified in $eventmask. |
242 | when at least one of events specified in $eventmask occurs. |
179 | |
243 | |
180 | The $eventmask can be one or more of these constants ORed together: |
244 | The $eventmask can be one or more of these constants ORed together: |
181 | |
245 | |
182 | EV::READ wait until read() wouldn't block anymore |
246 | EV::READ wait until read() wouldn't block anymore |
183 | EV::WRITE wait until write() wouldn't block anymore |
247 | EV::WRITE wait until write() wouldn't block anymore |
… | |
… | |
195 | |
259 | |
196 | $current_eventmask = $w->events |
260 | $current_eventmask = $w->events |
197 | $old_eventmask = $w->events ($new_eventmask) |
261 | $old_eventmask = $w->events ($new_eventmask) |
198 | Returns the previously set event mask and optionally set a new one. |
262 | Returns the previously set event mask and optionally set a new one. |
199 | |
263 | |
|
|
264 | TIMER WATCHERS - relative and optionally repeating timeouts |
200 | $w = EV::timer $after, $repeat, $callback |
265 | $w = EV::timer $after, $repeat, $callback |
201 | $w = EV::timer_ns $after, $repeat, $callback |
266 | $w = EV::timer_ns $after, $repeat, $callback |
202 | Calls the callback after $after seconds. If $repeat is non-zero, the |
267 | Calls the callback after $after seconds (which may be fractional). |
203 | timer will be restarted (with the $repeat value as $after) after the |
268 | If $repeat is non-zero, the timer will be restarted (with the |
204 | callback returns. |
269 | $repeat value as $after) after the callback returns. |
205 | |
270 | |
206 | This means that the callback would be called roughly after $after |
271 | This means that the callback would be called roughly after $after |
207 | seconds, and then every $repeat seconds. The timer does his best not |
272 | seconds, and then every $repeat seconds. The timer does his best not |
208 | to drift, but it will not invoke the timer more often then once per |
273 | to drift, but it will not invoke the timer more often then once per |
209 | event loop iteration, and might drift in other cases. If that isn't |
274 | event loop iteration, and might drift in other cases. If that isn't |
… | |
… | |
218 | The "timer_ns" variant doesn't start (activate) the newly created |
283 | The "timer_ns" variant doesn't start (activate) the newly created |
219 | watcher. |
284 | watcher. |
220 | |
285 | |
221 | $w->set ($after, $repeat) |
286 | $w->set ($after, $repeat) |
222 | Reconfigures the watcher, see the constructor above for details. Can |
287 | Reconfigures the watcher, see the constructor above for details. Can |
223 | be at any time. |
288 | be called at any time. |
224 | |
289 | |
225 | $w->again |
290 | $w->again |
226 | Similar to the "start" method, but has special semantics for |
291 | Similar to the "start" method, but has special semantics for |
227 | repeating timers: |
292 | repeating timers: |
228 | |
293 | |
… | |
… | |
239 | This behaviour is useful when you have a timeout for some IO |
304 | This behaviour is useful when you have a timeout for some IO |
240 | operation. You create a timer object with the same value for $after |
305 | operation. You create a timer object with the same value for $after |
241 | and $repeat, and then, in the read/write watcher, run the "again" |
306 | and $repeat, and then, in the read/write watcher, run the "again" |
242 | method on the timeout. |
307 | method on the timeout. |
243 | |
308 | |
|
|
309 | PERIODIC WATCHERS - to cron or not to cron? |
244 | $w = EV::periodic $at, $interval, $reschedule_cb, $callback |
310 | $w = EV::periodic $at, $interval, $reschedule_cb, $callback |
245 | $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback |
311 | $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback |
246 | Similar to EV::timer, but is not based on relative timeouts but on |
312 | Similar to EV::timer, but is not based on relative timeouts but on |
247 | absolute times. Apart from creating "simple" timers that trigger |
313 | absolute times. Apart from creating "simple" timers that trigger |
248 | "at" the specified time, it can also be used for non-drifting |
314 | "at" the specified time, it can also be used for non-drifting |
… | |
… | |
313 | The "periodic_ns" variant doesn't start (activate) the newly created |
379 | The "periodic_ns" variant doesn't start (activate) the newly created |
314 | watcher. |
380 | watcher. |
315 | |
381 | |
316 | $w->set ($at, $interval, $reschedule_cb) |
382 | $w->set ($at, $interval, $reschedule_cb) |
317 | Reconfigures the watcher, see the constructor above for details. Can |
383 | Reconfigures the watcher, see the constructor above for details. Can |
318 | be at any time. |
384 | be called at any time. |
319 | |
385 | |
320 | $w->again |
386 | $w->again |
321 | Simply stops and starts the watcher again. |
387 | Simply stops and starts the watcher again. |
322 | |
388 | |
|
|
389 | SIGNAL WATCHERS - signal me when a signal gets signalled! |
323 | $w = EV::signal $signal, $callback |
390 | $w = EV::signal $signal, $callback |
324 | $w = EV::signal_ns $signal, $callback |
391 | $w = EV::signal_ns $signal, $callback |
325 | Call the callback when $signal is received (the signal can be |
392 | Call the callback when $signal is received (the signal can be |
326 | specified by number or by name, just as with kill or %SIG). |
393 | specified by number or by name, just as with "kill" or %SIG). |
327 | |
394 | |
328 | EV will grab the signal for the process (the kernel only allows one |
395 | EV will grab the signal for the process (the kernel only allows one |
329 | component to receive a signal at a time) when you start a signal |
396 | component to receive a signal at a time) when you start a signal |
330 | watcher, and removes it again when you stop it. Perl does the same |
397 | watcher, and removes it again when you stop it. Perl does the same |
331 | when you add/remove callbacks to %SIG, so watch out. |
398 | when you add/remove callbacks to %SIG, so watch out. |
… | |
… | |
335 | The "signal_ns" variant doesn't start (activate) the newly created |
402 | The "signal_ns" variant doesn't start (activate) the newly created |
336 | watcher. |
403 | watcher. |
337 | |
404 | |
338 | $w->set ($signal) |
405 | $w->set ($signal) |
339 | Reconfigures the watcher, see the constructor above for details. Can |
406 | Reconfigures the watcher, see the constructor above for details. Can |
340 | be at any time. |
407 | be called at any time. |
341 | |
408 | |
342 | $current_signum = $w->signal |
409 | $current_signum = $w->signal |
343 | $old_signum = $w->signal ($new_signal) |
410 | $old_signum = $w->signal ($new_signal) |
344 | Returns the previously set signal (always as a number not name) and |
411 | Returns the previously set signal (always as a number not name) and |
345 | optionally set a new one. |
412 | optionally set a new one. |
346 | |
413 | |
|
|
414 | CHILD WATCHERS - watch out for process status changes |
347 | $w = EV::child $pid, $callback |
415 | $w = EV::child $pid, $callback |
348 | $w = EV::child_ns $pid, $callback |
416 | $w = EV::child_ns $pid, $callback |
349 | Call the callback when a status change for pid $pid (or any pid if |
417 | Call the callback when a status change for pid $pid (or any pid if |
350 | $pid is 0) has been received. More precisely: when the process |
418 | $pid is 0) has been received. More precisely: when the process |
351 | receives a SIGCHLD, EV will fetch the outstanding exit/wait status |
419 | receives a "SIGCHLD", EV will fetch the outstanding exit/wait status |
352 | for all changed/zombie children and call the callback. |
420 | for all changed/zombie children and call the callback. |
353 | |
421 | |
354 | You can access both status and pid by using the "rstatus" and "rpid" |
422 | It is valid (and fully supported) to install a child watcher after a |
|
|
423 | child has exited but before the event loop has started its next |
|
|
424 | iteration (for example, first you "fork", then the new child process |
|
|
425 | might exit, and only then do you install a child watcher in the |
|
|
426 | parent for the new pid). |
|
|
427 | |
|
|
428 | You can access both exit (or tracing) status and pid by using the |
355 | methods on the watcher object. |
429 | "rstatus" and "rpid" methods on the watcher object. |
356 | |
430 | |
357 | You can have as many pid watchers per pid as you want. |
431 | You can have as many pid watchers per pid as you want, they will all |
|
|
432 | be called. |
358 | |
433 | |
359 | The "child_ns" variant doesn't start (activate) the newly created |
434 | The "child_ns" variant doesn't start (activate) the newly created |
360 | watcher. |
435 | watcher. |
361 | |
436 | |
362 | $w->set ($pid) |
437 | $w->set ($pid) |
363 | Reconfigures the watcher, see the constructor above for details. Can |
438 | Reconfigures the watcher, see the constructor above for details. Can |
364 | be at any time. |
439 | be called at any time. |
365 | |
440 | |
366 | $current_pid = $w->pid |
441 | $current_pid = $w->pid |
367 | $old_pid = $w->pid ($new_pid) |
442 | $old_pid = $w->pid ($new_pid) |
368 | Returns the previously set process id and optionally set a new one. |
443 | Returns the previously set process id and optionally set a new one. |
369 | |
444 | |
… | |
… | |
373 | |
448 | |
374 | $pid = $w->rpid |
449 | $pid = $w->rpid |
375 | Return the pid of the awaited child (useful when you have installed |
450 | Return the pid of the awaited child (useful when you have installed |
376 | a watcher for all pids). |
451 | a watcher for all pids). |
377 | |
452 | |
|
|
453 | STAT WATCHERS - did the file attributes just change? |
|
|
454 | $w = EV::stat $path, $interval, $callback |
|
|
455 | $w = EV::stat_ns $path, $interval, $callback |
|
|
456 | Call the callback when a file status change has been detected on |
|
|
457 | $path. The $path does not need to exist, changing from "path exists" |
|
|
458 | to "path does not exist" is a status change like any other. |
|
|
459 | |
|
|
460 | The $interval is a recommended polling interval for systems where |
|
|
461 | OS-supported change notifications don't exist or are not supported. |
|
|
462 | If you use 0 then an unspecified default is used (which is highly |
|
|
463 | recommended!), which is to be expected to be around five seconds |
|
|
464 | usually. |
|
|
465 | |
|
|
466 | This watcher type is not meant for massive numbers of stat watchers, |
|
|
467 | as even with OS-supported change notifications, this can be |
|
|
468 | resource-intensive. |
|
|
469 | |
|
|
470 | The "stat_ns" variant doesn't start (activate) the newly created |
|
|
471 | watcher. |
|
|
472 | |
|
|
473 | $w->set ($path, $interval) |
|
|
474 | Reconfigures the watcher, see the constructor above for details. Can |
|
|
475 | be called at any time. |
|
|
476 | |
|
|
477 | $current_path = $w->path |
|
|
478 | $old_path = $w->path ($new_path) |
|
|
479 | Returns the previously set path and optionally set a new one. |
|
|
480 | |
|
|
481 | $current_interval = $w->interval |
|
|
482 | $old_interval = $w->interval ($new_interval) |
|
|
483 | Returns the previously set interval and optionally set a new one. |
|
|
484 | Can be used to query the actual interval used. |
|
|
485 | |
|
|
486 | IDLE WATCHERS - when you've got nothing better to do... |
378 | $w = EV::idle $callback |
487 | $w = EV::idle $callback |
379 | $w = EV::idle_ns $callback |
488 | $w = EV::idle_ns $callback |
380 | Call the callback when there are no pending io, timer/periodic, |
489 | Call the callback when there are no pending io, timer/periodic, |
381 | signal or child events, i.e. when the process is idle. |
490 | signal or child events, i.e. when the process is idle. |
382 | |
491 | |
… | |
… | |
384 | and they will be called repeatedly until stopped. |
493 | and they will be called repeatedly until stopped. |
385 | |
494 | |
386 | The "idle_ns" variant doesn't start (activate) the newly created |
495 | The "idle_ns" variant doesn't start (activate) the newly created |
387 | watcher. |
496 | watcher. |
388 | |
497 | |
|
|
498 | PREPARE WATCHERS - customise your event loop! |
389 | $w = EV::prepare $callback |
499 | $w = EV::prepare $callback |
390 | $w = EV::prepare_ns $callback |
500 | $w = EV::prepare_ns $callback |
391 | Call the callback just before the process would block. You can still |
501 | Call the callback just before the process would block. You can still |
392 | create/modify any watchers at this point. |
502 | create/modify any watchers at this point. |
393 | |
503 | |
394 | See the EV::check watcher, below, for explanations and an example. |
504 | See the EV::check watcher, below, for explanations and an example. |
395 | |
505 | |
396 | The "prepare_ns" variant doesn't start (activate) the newly created |
506 | The "prepare_ns" variant doesn't start (activate) the newly created |
397 | watcher. |
507 | watcher. |
398 | |
508 | |
|
|
509 | CHECK WATCHERS - customise your event loop even more! |
399 | $w = EV::check $callback |
510 | $w = EV::check $callback |
400 | $w = EV::check_ns $callback |
511 | $w = EV::check_ns $callback |
401 | Call the callback just after the process wakes up again (after it |
512 | Call the callback just after the process wakes up again (after it |
402 | has gathered events), but before any other callbacks have been |
513 | has gathered events), but before any other callbacks have been |
403 | invoked. |
514 | invoked. |
… | |
… | |
414 | # do nothing unless active |
525 | # do nothing unless active |
415 | $dispatcher->{_event_queue_h} |
526 | $dispatcher->{_event_queue_h} |
416 | or return; |
527 | or return; |
417 | |
528 | |
418 | # make the dispatcher handle any outstanding stuff |
529 | # make the dispatcher handle any outstanding stuff |
|
|
530 | ... not shown |
419 | |
531 | |
420 | # create an IO watcher for each and every socket |
532 | # create an IO watcher for each and every socket |
421 | @snmp_watcher = ( |
533 | @snmp_watcher = ( |
422 | (map { EV::io $_, EV::READ, sub { } } |
534 | (map { EV::io $_, EV::READ, sub { } } |
423 | keys %{ $dispatcher->{_descriptors} }), |
535 | keys %{ $dispatcher->{_descriptors} }), |
|
|
536 | |
|
|
537 | EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE] |
|
|
538 | ? $event->[Net::SNMP::Dispatcher::_TIME] - EV::now : 0), |
|
|
539 | 0, sub { }, |
424 | ); |
540 | ); |
425 | |
|
|
426 | # if there are any timeouts, also create a timer |
|
|
427 | push @snmp_watcher, EV::timer $event->[Net::SNMP::Dispatcher::_TIME] - EV::now, 0, sub { } |
|
|
428 | if $event->[Net::SNMP::Dispatcher::_ACTIVE]; |
|
|
429 | }; |
541 | }; |
430 | |
542 | |
431 | The callbacks are irrelevant, the only purpose of those watchers is |
543 | The callbacks are irrelevant (and are not even being called), the |
432 | to wake up the process as soon as one of those events occurs (socket |
544 | only purpose of those watchers is to wake up the process as soon as |
433 | readable, or timer timed out). The corresponding EV::check watcher |
545 | one of those events occurs (socket readable, or timer timed out). |
434 | will then clean up: |
546 | The corresponding EV::check watcher will then clean up: |
435 | |
547 | |
436 | our $snmp_check = EV::check sub { |
548 | our $snmp_check = EV::check sub { |
437 | # destroy all watchers |
549 | # destroy all watchers |
438 | @snmp_watcher = (); |
550 | @snmp_watcher = (); |
439 | |
551 | |
440 | # make the dispatcher handle any new stuff |
552 | # make the dispatcher handle any new stuff |
|
|
553 | ... not shown |
441 | }; |
554 | }; |
442 | |
555 | |
443 | The callbacks of the created watchers will not be called as the |
556 | The callbacks of the created watchers will not be called as the |
444 | watchers are destroyed before this cna happen (remember EV::check |
557 | watchers are destroyed before this cna happen (remember EV::check |
445 | gets called first). |
558 | gets called first). |
446 | |
559 | |
447 | The "check_ns" variant doesn't start (activate) the newly created |
560 | The "check_ns" variant doesn't start (activate) the newly created |
448 | watcher. |
561 | watcher. |
449 | |
562 | |
|
|
563 | FORK WATCHERS - the audacity to resume the event loop after a fork |
|
|
564 | Fork watchers are called when a "fork ()" was detected. The invocation |
|
|
565 | is done before the event loop blocks next and before "check" watchers |
|
|
566 | are being called, and only in the child after the fork. |
|
|
567 | |
|
|
568 | $w = EV::fork $callback |
|
|
569 | $w = EV::fork_ns $callback |
|
|
570 | Call the callback before the event loop is resumed in the child |
|
|
571 | process after a fork. |
|
|
572 | |
|
|
573 | The "fork_ns" variant doesn't start (activate) the newly created |
|
|
574 | watcher. |
|
|
575 | |
450 | THREADS |
576 | THREADS |
451 | Threads are not supported by this in any way. Perl pseudo-threads is |
577 | Threads are not supported by this module in any way. Perl pseudo-threads |
452 | evil stuff and must die. |
578 | is evil stuff and must die. As soon as Perl gains real threads I will |
|
|
579 | work on thread support for it. |
|
|
580 | |
|
|
581 | FORK |
|
|
582 | Most of the "improved" event delivering mechanisms of modern operating |
|
|
583 | systems have quite a few problems with fork(2) (to put it bluntly: it is |
|
|
584 | not supported and usually destructive). Libev makes it possible to work |
|
|
585 | around this by having a function that recreates the kernel state after |
|
|
586 | fork in the child. |
|
|
587 | |
|
|
588 | On non-win32 platforms, this module requires the pthread_atfork |
|
|
589 | functionality to do this automatically for you. This function is quite |
|
|
590 | buggy on most BSDs, though, so YMMV. The overhead for this is quite |
|
|
591 | negligible, because everything the function currently does is set a flag |
|
|
592 | that is checked only when the event loop gets used the next time, so |
|
|
593 | when you do fork but not use EV, the overhead is minimal. |
|
|
594 | |
|
|
595 | On win32, there is no notion of fork so all this doesn't apply, of |
|
|
596 | course. |
453 | |
597 | |
454 | SEE ALSO |
598 | SEE ALSO |
455 | L<EV::DNS>. |
599 | EV::DNS. |
456 | |
600 | |
457 | AUTHOR |
601 | AUTHOR |
458 | Marc Lehmann <schmorp@schmorp.de> |
602 | Marc Lehmann <schmorp@schmorp.de> |
459 | http://home.schmorp.de/ |
603 | http://home.schmorp.de/ |
460 | |
604 | |