1 |
root |
1.1 |
NAME |
2 |
root |
1.6 |
EV - perl interface to libev, a high performance full-featured event |
3 |
|
|
loop |
4 |
root |
1.1 |
|
5 |
root |
1.2 |
SYNOPSIS |
6 |
root |
1.28 |
use EV; |
7 |
|
|
|
8 |
|
|
# TIMERS |
9 |
|
|
|
10 |
|
|
my $w = EV::timer 2, 0, sub { |
11 |
|
|
warn "is called after 2s"; |
12 |
|
|
}; |
13 |
|
|
|
14 |
|
|
my $w = EV::timer 2, 2, sub { |
15 |
|
|
warn "is called roughly every 2s (repeat = 2)"; |
16 |
|
|
}; |
17 |
|
|
|
18 |
|
|
undef $w; # destroy event watcher again |
19 |
|
|
|
20 |
|
|
my $w = EV::periodic 0, 60, 0, sub { |
21 |
|
|
warn "is called every minute, on the minute, exactly"; |
22 |
|
|
}; |
23 |
|
|
|
24 |
|
|
# IO |
25 |
|
|
|
26 |
|
|
my $w = EV::io *STDIN, EV::READ, sub { |
27 |
|
|
my ($w, $revents) = @_; # all callbacks receive the watcher and event mask |
28 |
|
|
warn "stdin is readable, you entered: ", <STDIN>; |
29 |
|
|
}; |
30 |
|
|
|
31 |
|
|
# SIGNALS |
32 |
|
|
|
33 |
|
|
my $w = EV::signal 'QUIT', sub { |
34 |
|
|
warn "sigquit received\n"; |
35 |
|
|
}; |
36 |
|
|
|
37 |
|
|
# CHILD/PID STATUS CHANGES |
38 |
|
|
|
39 |
|
|
my $w = EV::child 666, 0, sub { |
40 |
|
|
my ($w, $revents) = @_; |
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"; |
48 |
|
|
}; |
49 |
|
|
|
50 |
|
|
# MAINLOOP |
51 |
|
|
EV::loop; # loop until EV::unloop is called or all watchers stop |
52 |
|
|
EV::loop EV::LOOP_ONESHOT; # block until at least one event could be handled |
53 |
|
|
EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block |
54 |
root |
1.2 |
|
55 |
|
|
DESCRIPTION |
56 |
root |
1.5 |
This module provides an interface to libev |
57 |
root |
1.12 |
(<http://software.schmorp.de/pkg/libev.html>). While the documentation |
58 |
|
|
below is comprehensive, one might also consult the documentation of |
59 |
root |
1.30 |
libev itself (<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod> or |
60 |
|
|
perldoc EV::libev) for more subtle details on watcher semantics or some |
61 |
|
|
discussion on the available backends, or how to force a specific backend |
62 |
|
|
with "LIBEV_FLAGS", or just about in any case because it has much more |
63 |
root |
1.25 |
detailed information. |
64 |
|
|
|
65 |
|
|
This module is very fast and scalable. It is actually so fast that you |
66 |
|
|
can use it through the AnyEvent module, stay portable to other event |
67 |
|
|
loops (if you don't rely on any watcher types not available through it) |
68 |
|
|
and still be faster than with any other event loop currently supported |
69 |
|
|
in Perl. |
70 |
root |
1.2 |
|
71 |
root |
1.30 |
MODULE EXPORTS |
72 |
|
|
This module does not export any symbols. |
73 |
|
|
|
74 |
root |
1.20 |
EVENT LOOPS |
75 |
|
|
EV supports multiple event loops: There is a single "default event loop" |
76 |
|
|
that can handle everything including signals and child watchers, and any |
77 |
|
|
number of "dynamic event loops" that can use different backends (with |
78 |
|
|
various limitations), but no child and signal watchers. |
79 |
|
|
|
80 |
|
|
You do not have to do anything to create the default event loop: When |
81 |
|
|
the module is loaded a suitable backend is selected on the premise of |
82 |
|
|
selecting a working backend (which for example rules out kqueue on most |
83 |
|
|
BSDs). Modules should, unless they have "special needs" always use the |
84 |
|
|
default loop as this is fastest (perl-wise), best supported by other |
85 |
|
|
modules (e.g. AnyEvent or Coro) and most portable event loop. |
86 |
|
|
|
87 |
root |
1.21 |
For specific programs you can create additional event loops dynamically. |
88 |
root |
1.20 |
|
89 |
root |
1.31 |
If you want to take advantage of kqueue (which often works properly for |
90 |
root |
1.28 |
sockets only) even though the default loop doesn't enable it, you can |
91 |
|
|
*embed* a kqueue loop into the default loop: running the default loop |
92 |
|
|
will then also service the kqueue loop to some extent. See the example |
93 |
|
|
in the section about embed watchers for an example on how to achieve |
94 |
|
|
that. |
95 |
|
|
|
96 |
root |
1.20 |
$loop = new EV::loop [$flags] |
97 |
|
|
Create a new event loop as per the specified flags. Please refer to |
98 |
|
|
the "ev_loop_new ()" function description in the libev documentation |
99 |
|
|
(<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTI |
100 |
root |
1.30 |
ONS>, or locally-installed as EV::libev manpage) for more info. |
101 |
root |
1.20 |
|
102 |
|
|
The loop will automatically be destroyed when it is no longer |
103 |
|
|
referenced by any watcher and the loop object goes out of scope. |
104 |
|
|
|
105 |
root |
1.30 |
If you are not embedding the loop, then Using "EV::FLAG_FORKCHECK" |
106 |
|
|
is recommended, as only the default event loop is protected by this |
107 |
|
|
module. If you *are* embedding this loop in the default loop, this |
108 |
|
|
is not necessary, as "EV::embed" automatically does the right thing |
109 |
|
|
on fork. |
110 |
root |
1.20 |
|
111 |
|
|
$loop->loop_fork |
112 |
|
|
Must be called after a fork in the child, before entering or |
113 |
|
|
continuing the event loop. An alternative is to use |
114 |
root |
1.27 |
"EV::FLAG_FORKCHECK" which calls this function automatically, at |
115 |
root |
1.20 |
some performance loss (refer to the libev documentation). |
116 |
|
|
|
117 |
root |
1.27 |
$loop->loop_verify |
118 |
|
|
Calls "ev_verify" to make internal consistency checks (for debugging |
119 |
root |
1.28 |
libev) and abort the program if any data structures were found to be |
120 |
root |
1.27 |
corrupted. |
121 |
|
|
|
122 |
root |
1.21 |
$loop = EV::default_loop [$flags] |
123 |
root |
1.27 |
Return the default loop (which is a singleton object). Since this |
124 |
|
|
module already creates the default loop with default flags, |
125 |
|
|
specifying flags here will not have any effect unless you destroy |
126 |
root |
1.28 |
the default loop first, which isn't supported. So in short: don't do |
127 |
|
|
it, and if you break it, you get to keep the pieces. |
128 |
root |
1.21 |
|
129 |
root |
1.3 |
BASIC INTERFACE |
130 |
|
|
$EV::DIED |
131 |
|
|
Must contain a reference to a function that is called when a |
132 |
root |
1.18 |
callback throws an exception (with $@ containing the error). The |
133 |
root |
1.3 |
default prints an informative message and continues. |
134 |
|
|
|
135 |
|
|
If this callback throws an exception it will be silently ignored. |
136 |
|
|
|
137 |
root |
1.21 |
$flags = EV::supported_backends |
138 |
|
|
$flags = EV::recommended_backends |
139 |
|
|
$flags = EV::embeddable_backends |
140 |
|
|
Returns the set (see "EV::BACKEND_*" flags) of backends supported by |
141 |
|
|
this instance of EV, the set of recommended backends (supposed to be |
142 |
|
|
good) for this platform and the set of embeddable backends (see |
143 |
|
|
EMBED WATCHERS). |
144 |
|
|
|
145 |
|
|
EV::sleep $seconds |
146 |
|
|
Block the process for the given number of (fractional) seconds. |
147 |
|
|
|
148 |
root |
1.6 |
$time = EV::time |
149 |
|
|
Returns the current time in (fractional) seconds since the epoch. |
150 |
|
|
|
151 |
root |
1.2 |
$time = EV::now |
152 |
root |
1.20 |
$time = $loop->now |
153 |
root |
1.6 |
Returns the time the last event loop iteration has been started. |
154 |
root |
1.31 |
This is the time that (relative) timers are based on, and referring |
155 |
root |
1.6 |
to it is usually faster then calling EV::time. |
156 |
|
|
|
157 |
root |
1.20 |
$backend = EV::backend |
158 |
|
|
$backend = $loop->backend |
159 |
root |
1.6 |
Returns an integer describing the backend used by libev |
160 |
root |
1.31 |
(EV::BACKEND_SELECT or EV::BACKEND_EPOLL). |
161 |
root |
1.6 |
|
162 |
|
|
EV::loop [$flags] |
163 |
root |
1.20 |
$loop->loop ([$flags]) |
164 |
root |
1.6 |
Begin checking for events and calling callbacks. It returns when a |
165 |
root |
1.10 |
callback calls EV::unloop. |
166 |
root |
1.6 |
|
167 |
|
|
The $flags argument can be one of the following: |
168 |
|
|
|
169 |
|
|
0 as above |
170 |
|
|
EV::LOOP_ONESHOT block at most once (wait, but do not loop) |
171 |
|
|
EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait) |
172 |
|
|
|
173 |
root |
1.10 |
EV::unloop [$how] |
174 |
root |
1.20 |
$loop->unloop ([$how]) |
175 |
root |
1.10 |
When called with no arguments or an argument of EV::UNLOOP_ONE, |
176 |
|
|
makes the innermost call to EV::loop return. |
177 |
root |
1.6 |
|
178 |
root |
1.10 |
When called with an argument of EV::UNLOOP_ALL, all calls to |
179 |
|
|
EV::loop will return as fast as possible. |
180 |
root |
1.6 |
|
181 |
root |
1.15 |
$count = EV::loop_count |
182 |
root |
1.20 |
$count = $loop->loop_count |
183 |
root |
1.15 |
Return the number of times the event loop has polled for new events. |
184 |
root |
1.31 |
Sometimes useful as a generation counter. |
185 |
root |
1.15 |
|
186 |
root |
1.12 |
EV::once $fh_or_undef, $events, $timeout, $cb->($revents) |
187 |
root |
1.20 |
$loop->once ($fh_or_undef, $events, $timeout, $cb->($revents)) |
188 |
root |
1.12 |
This function rolls together an I/O and a timer watcher for a single |
189 |
|
|
one-shot event without the need for managing a watcher object. |
190 |
|
|
|
191 |
|
|
If $fh_or_undef is a filehandle or file descriptor, then $events |
192 |
|
|
must be a bitset containing either "EV::READ", "EV::WRITE" or |
193 |
|
|
"EV::READ | EV::WRITE", indicating the type of I/O event you want to |
194 |
|
|
wait for. If you do not want to wait for some I/O event, specify |
195 |
|
|
"undef" for $fh_or_undef and 0 for $events). |
196 |
|
|
|
197 |
|
|
If timeout is "undef" or negative, then there will be no timeout. |
198 |
|
|
Otherwise a EV::timer with this value will be started. |
199 |
|
|
|
200 |
|
|
When an error occurs or either the timeout or I/O watcher triggers, |
201 |
|
|
then the callback will be called with the received event set (in |
202 |
root |
1.20 |
general you can expect it to be a combination of "EV::ERROR", |
203 |
root |
1.12 |
"EV::READ", "EV::WRITE" and "EV::TIMEOUT"). |
204 |
|
|
|
205 |
|
|
EV::once doesn't return anything: the watchers stay active till |
206 |
|
|
either of them triggers, then they will be stopped and freed, and |
207 |
|
|
the callback invoked. |
208 |
|
|
|
209 |
root |
1.17 |
EV::feed_fd_event ($fd, $revents) |
210 |
root |
1.20 |
$loop->feed_fd_event ($fd, $revents) |
211 |
root |
1.17 |
Feed an event on a file descriptor into EV. EV will react to this |
212 |
|
|
call as if the readyness notifications specified by $revents (a |
213 |
|
|
combination of "EV::READ" and "EV::WRITE") happened on the file |
214 |
|
|
descriptor $fd. |
215 |
|
|
|
216 |
|
|
EV::feed_signal_event ($signal) |
217 |
|
|
Feed a signal event into EV. EV will react to this call as if the |
218 |
|
|
signal specified by $signal had occured. |
219 |
|
|
|
220 |
root |
1.21 |
EV::set_io_collect_interval $time |
221 |
|
|
$loop->set_io_collect_interval ($time) |
222 |
|
|
EV::set_timeout_collect_interval $time |
223 |
|
|
$loop->set_timeout_collect_interval ($time) |
224 |
|
|
These advanced functions set the minimum block interval when polling |
225 |
|
|
for I/O events and the minimum wait interval for timer events. See |
226 |
|
|
the libev documentation at |
227 |
|
|
<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONT |
228 |
root |
1.30 |
ROLLING_THE_EVENT_LOOP> (locally installed as EV::libev) for a more |
229 |
|
|
detailed discussion. |
230 |
root |
1.21 |
|
231 |
root |
1.20 |
WATCHER OBJECTS |
232 |
root |
1.6 |
A watcher is an object that gets created to record your interest in some |
233 |
|
|
event. For instance, if you want to wait for STDIN to become readable, |
234 |
|
|
you would create an EV::io watcher for that: |
235 |
|
|
|
236 |
root |
1.28 |
my $watcher = EV::io *STDIN, EV::READ, sub { |
237 |
|
|
my ($watcher, $revents) = @_; |
238 |
|
|
warn "yeah, STDIN should now be readable without blocking!\n" |
239 |
|
|
}; |
240 |
root |
1.2 |
|
241 |
root |
1.6 |
All watchers can be active (waiting for events) or inactive (paused). |
242 |
|
|
Only active watchers will have their callbacks invoked. All callbacks |
243 |
|
|
will be called with at least two arguments: the watcher and a bitmask of |
244 |
|
|
received events. |
245 |
|
|
|
246 |
|
|
Each watcher type has its associated bit in revents, so you can use the |
247 |
|
|
same callback for multiple watchers. The event mask is named after the |
248 |
root |
1.31 |
type, i.e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, |
249 |
root |
1.16 |
EV::periodic sets EV::PERIODIC and so on, with the exception of I/O |
250 |
root |
1.6 |
events (which can set both EV::READ and EV::WRITE bits), and EV::timer |
251 |
|
|
(which uses EV::TIMEOUT). |
252 |
|
|
|
253 |
|
|
In the rare case where one wants to create a watcher but not start it at |
254 |
|
|
the same time, each constructor has a variant with a trailing "_ns" in |
255 |
|
|
its name, e.g. EV::io has a non-starting variant EV::io_ns and so on. |
256 |
|
|
|
257 |
|
|
Please note that a watcher will automatically be stopped when the |
258 |
root |
1.7 |
watcher object is destroyed, so you *need* to keep the watcher objects |
259 |
root |
1.6 |
returned by the constructors. |
260 |
|
|
|
261 |
root |
1.7 |
Also, all methods changing some aspect of a watcher (->set, ->priority, |
262 |
|
|
->fh and so on) automatically stop and start it again if it is active, |
263 |
|
|
which means pending events get lost. |
264 |
|
|
|
265 |
root |
1.13 |
COMMON WATCHER METHODS |
266 |
|
|
This section lists methods common to all watchers. |
267 |
root |
1.2 |
|
268 |
root |
1.6 |
$w->start |
269 |
|
|
Starts a watcher if it isn't active already. Does nothing to an |
270 |
|
|
already active watcher. By default, all watchers start out in the |
271 |
|
|
active state (see the description of the "_ns" variants if you need |
272 |
|
|
stopped watchers). |
273 |
|
|
|
274 |
|
|
$w->stop |
275 |
|
|
Stop a watcher if it is active. Also clear any pending events |
276 |
|
|
(events that have been received but that didn't yet result in a |
277 |
root |
1.16 |
callback invocation), regardless of whether the watcher was active |
278 |
|
|
or not. |
279 |
root |
1.6 |
|
280 |
|
|
$bool = $w->is_active |
281 |
|
|
Returns true if the watcher is active, false otherwise. |
282 |
|
|
|
283 |
root |
1.8 |
$current_data = $w->data |
284 |
|
|
$old_data = $w->data ($new_data) |
285 |
|
|
Queries a freely usable data scalar on the watcher and optionally |
286 |
|
|
changes it. This is a way to associate custom data with a watcher: |
287 |
|
|
|
288 |
|
|
my $w = EV::timer 60, 0, sub { |
289 |
|
|
warn $_[0]->data; |
290 |
|
|
}; |
291 |
|
|
$w->data ("print me!"); |
292 |
|
|
|
293 |
root |
1.6 |
$current_cb = $w->cb |
294 |
|
|
$old_cb = $w->cb ($new_cb) |
295 |
|
|
Queries the callback on the watcher and optionally changes it. You |
296 |
root |
1.7 |
can do this at any time without the watcher restarting. |
297 |
|
|
|
298 |
|
|
$current_priority = $w->priority |
299 |
|
|
$old_priority = $w->priority ($new_priority) |
300 |
|
|
Queries the priority on the watcher and optionally changes it. |
301 |
|
|
Pending watchers with higher priority will be invoked first. The |
302 |
|
|
valid range of priorities lies between EV::MAXPRI (default 2) and |
303 |
|
|
EV::MINPRI (default -2). If the priority is outside this range it |
304 |
|
|
will automatically be normalised to the nearest valid priority. |
305 |
|
|
|
306 |
root |
1.12 |
The default priority of any newly-created watcher is 0. |
307 |
|
|
|
308 |
|
|
Note that the priority semantics have not yet been fleshed out and |
309 |
|
|
are subject to almost certain change. |
310 |
root |
1.2 |
|
311 |
root |
1.17 |
$w->invoke ($revents) |
312 |
root |
1.6 |
Call the callback *now* with the given event mask. |
313 |
root |
1.2 |
|
314 |
root |
1.17 |
$w->feed_event ($revents) |
315 |
|
|
Feed some events on this watcher into EV. EV will react to this call |
316 |
|
|
as if the watcher had received the given $revents mask. |
317 |
|
|
|
318 |
|
|
$revents = $w->clear_pending |
319 |
root |
1.20 |
If the watcher is pending, this function clears its pending status |
320 |
|
|
and returns its $revents bitset (as if its callback was invoked). If |
321 |
|
|
the watcher isn't pending it does nothing and returns 0. |
322 |
root |
1.17 |
|
323 |
root |
1.12 |
$previous_state = $w->keepalive ($bool) |
324 |
|
|
Normally, "EV::loop" will return when there are no active watchers |
325 |
|
|
(which is a "deadlock" because no progress can be made anymore). |
326 |
|
|
This is convinient because it allows you to start your watchers (and |
327 |
|
|
your jobs), call "EV::loop" once and when it returns you know that |
328 |
|
|
all your jobs are finished (or they forgot to register some watchers |
329 |
|
|
for their task :). |
330 |
|
|
|
331 |
root |
1.20 |
Sometimes, however, this gets in your way, for example when the |
332 |
root |
1.12 |
module that calls "EV::loop" (usually the main program) is not the |
333 |
|
|
same module as a long-living watcher (for example a DNS client |
334 |
|
|
module written by somebody else even). Then you might want any |
335 |
|
|
outstanding requests to be handled, but you would not want to keep |
336 |
|
|
"EV::loop" from returning just because you happen to have this |
337 |
|
|
long-running UDP port watcher. |
338 |
|
|
|
339 |
|
|
In this case you can clear the keepalive status, which means that |
340 |
|
|
even though your watcher is active, it won't keep "EV::loop" from |
341 |
|
|
returning. |
342 |
|
|
|
343 |
root |
1.31 |
The initial value for keepalive is true (enabled), and you can |
344 |
root |
1.12 |
change it any time. |
345 |
|
|
|
346 |
root |
1.16 |
Example: Register an I/O watcher for some UDP socket but do not keep |
347 |
root |
1.12 |
the event loop from running just because of that watcher. |
348 |
|
|
|
349 |
|
|
my $udp_socket = ... |
350 |
|
|
my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... }; |
351 |
root |
1.28 |
$udp_watcher->keepalive (0); |
352 |
root |
1.20 |
|
353 |
|
|
$loop = $w->loop |
354 |
|
|
Return the loop that this watcher is attached to. |
355 |
root |
1.12 |
|
356 |
root |
1.20 |
WATCHER TYPES |
357 |
root |
1.13 |
Each of the following subsections describes a single watcher type. |
358 |
|
|
|
359 |
root |
1.16 |
I/O WATCHERS - is this file descriptor readable or writable? |
360 |
root |
1.6 |
$w = EV::io $fileno_or_fh, $eventmask, $callback |
361 |
|
|
$w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
362 |
root |
1.20 |
$w = $loop->io ($fileno_or_fh, $eventmask, $callback) |
363 |
|
|
$w = $loop->io_ns ($fileno_or_fh, $eventmask, $callback) |
364 |
root |
1.6 |
As long as the returned watcher object is alive, call the $callback |
365 |
root |
1.13 |
when at least one of events specified in $eventmask occurs. |
366 |
root |
1.2 |
|
367 |
root |
1.6 |
The $eventmask can be one or more of these constants ORed together: |
368 |
root |
1.1 |
|
369 |
root |
1.2 |
EV::READ wait until read() wouldn't block anymore |
370 |
|
|
EV::WRITE wait until write() wouldn't block anymore |
371 |
|
|
|
372 |
root |
1.6 |
The "io_ns" variant doesn't start (activate) the newly created |
373 |
|
|
watcher. |
374 |
|
|
|
375 |
|
|
$w->set ($fileno_or_fh, $eventmask) |
376 |
|
|
Reconfigures the watcher, see the constructor above for details. Can |
377 |
|
|
be called at any time. |
378 |
|
|
|
379 |
|
|
$current_fh = $w->fh |
380 |
|
|
$old_fh = $w->fh ($new_fh) |
381 |
|
|
Returns the previously set filehandle and optionally set a new one. |
382 |
|
|
|
383 |
|
|
$current_eventmask = $w->events |
384 |
|
|
$old_eventmask = $w->events ($new_eventmask) |
385 |
|
|
Returns the previously set event mask and optionally set a new one. |
386 |
|
|
|
387 |
root |
1.13 |
TIMER WATCHERS - relative and optionally repeating timeouts |
388 |
root |
1.6 |
$w = EV::timer $after, $repeat, $callback |
389 |
|
|
$w = EV::timer_ns $after, $repeat, $callback |
390 |
root |
1.20 |
$w = $loop->timer ($after, $repeat, $callback) |
391 |
|
|
$w = $loop->timer_ns ($after, $repeat, $callback) |
392 |
root |
1.12 |
Calls the callback after $after seconds (which may be fractional). |
393 |
|
|
If $repeat is non-zero, the timer will be restarted (with the |
394 |
|
|
$repeat value as $after) after the callback returns. |
395 |
root |
1.6 |
|
396 |
|
|
This means that the callback would be called roughly after $after |
397 |
root |
1.10 |
seconds, and then every $repeat seconds. The timer does his best not |
398 |
|
|
to drift, but it will not invoke the timer more often then once per |
399 |
|
|
event loop iteration, and might drift in other cases. If that isn't |
400 |
|
|
acceptable, look at EV::periodic, which can provide long-term stable |
401 |
|
|
timers. |
402 |
root |
1.6 |
|
403 |
root |
1.10 |
The timer is based on a monotonic clock, that is, if somebody is |
404 |
root |
1.6 |
sitting in front of the machine while the timer is running and |
405 |
|
|
changes the system clock, the timer will nevertheless run (roughly) |
406 |
|
|
the same time. |
407 |
|
|
|
408 |
|
|
The "timer_ns" variant doesn't start (activate) the newly created |
409 |
|
|
watcher. |
410 |
|
|
|
411 |
|
|
$w->set ($after, $repeat) |
412 |
|
|
Reconfigures the watcher, see the constructor above for details. Can |
413 |
root |
1.13 |
be called at any time. |
414 |
root |
1.6 |
|
415 |
|
|
$w->again |
416 |
|
|
Similar to the "start" method, but has special semantics for |
417 |
|
|
repeating timers: |
418 |
root |
1.2 |
|
419 |
root |
1.10 |
If the timer is active and non-repeating, it will be stopped. |
420 |
|
|
|
421 |
root |
1.6 |
If the timer is active and repeating, reset the timeout to occur |
422 |
|
|
$repeat seconds after now. |
423 |
root |
1.2 |
|
424 |
root |
1.10 |
If the timer is inactive and repeating, start it using the repeat |
425 |
|
|
value. |
426 |
root |
1.6 |
|
427 |
|
|
Otherwise do nothing. |
428 |
|
|
|
429 |
|
|
This behaviour is useful when you have a timeout for some IO |
430 |
|
|
operation. You create a timer object with the same value for $after |
431 |
|
|
and $repeat, and then, in the read/write watcher, run the "again" |
432 |
|
|
method on the timeout. |
433 |
|
|
|
434 |
root |
1.13 |
PERIODIC WATCHERS - to cron or not to cron? |
435 |
root |
1.8 |
$w = EV::periodic $at, $interval, $reschedule_cb, $callback |
436 |
|
|
$w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback |
437 |
root |
1.20 |
$w = $loop->periodic ($at, $interval, $reschedule_cb, $callback) |
438 |
|
|
$w = $loop->periodic_ns ($at, $interval, $reschedule_cb, $callback) |
439 |
root |
1.8 |
Similar to EV::timer, but is not based on relative timeouts but on |
440 |
|
|
absolute times. Apart from creating "simple" timers that trigger |
441 |
|
|
"at" the specified time, it can also be used for non-drifting |
442 |
|
|
absolute timers and more complex, cron-like, setups that are not |
443 |
|
|
adversely affected by time jumps (i.e. when the system clock is |
444 |
|
|
changed by explicit date -s or other means such as ntpd). It is also |
445 |
|
|
the most complex watcher type in EV. |
446 |
|
|
|
447 |
|
|
It has three distinct "modes": |
448 |
|
|
|
449 |
root |
1.22 |
* absolute timer ($interval = $reschedule_cb = 0) |
450 |
|
|
|
451 |
root |
1.8 |
This time simply fires at the wallclock time $at and doesn't |
452 |
|
|
repeat. It will not adjust when a time jump occurs, that is, if |
453 |
|
|
it is to be run at January 1st 2011 then it will run when the |
454 |
|
|
system time reaches or surpasses this time. |
455 |
|
|
|
456 |
root |
1.23 |
* repeating interval timer ($interval > 0, $reschedule_cb = 0) |
457 |
root |
1.22 |
|
458 |
root |
1.8 |
In this mode the watcher will always be scheduled to time out at |
459 |
|
|
the next "$at + N * $interval" time (for some integer N) and |
460 |
|
|
then repeat, regardless of any time jumps. |
461 |
|
|
|
462 |
|
|
This can be used to create timers that do not drift with respect |
463 |
|
|
to system time: |
464 |
|
|
|
465 |
|
|
my $hourly = EV::periodic 0, 3600, 0, sub { print "once/hour\n" }; |
466 |
|
|
|
467 |
|
|
That doesn't mean there will always be 3600 seconds in between |
468 |
|
|
triggers, but only that the the clalback will be called when the |
469 |
|
|
system time shows a full hour (UTC). |
470 |
|
|
|
471 |
|
|
Another way to think about it (for the mathematically inclined) |
472 |
|
|
is that EV::periodic will try to run the callback in this mode |
473 |
|
|
at the next possible time where "$time = $at (mod $interval)", |
474 |
|
|
regardless of any time jumps. |
475 |
|
|
|
476 |
root |
1.22 |
* manual reschedule mode ($reschedule_cb = coderef) |
477 |
|
|
|
478 |
root |
1.8 |
In this mode $interval and $at are both being ignored. Instead, |
479 |
root |
1.10 |
each time the periodic watcher gets scheduled, the reschedule |
480 |
root |
1.8 |
callback ($reschedule_cb) will be called with the watcher as |
481 |
|
|
first, and the current time as second argument. |
482 |
|
|
|
483 |
|
|
*This callback MUST NOT stop or destroy this or any other |
484 |
root |
1.26 |
periodic watcher, ever, and MUST NOT call any event loop |
485 |
|
|
functions or methods*. If you need to stop it, return 1e30 and |
486 |
|
|
stop it afterwards. You may create and start a "EV::prepare" |
487 |
|
|
watcher for this task. |
488 |
root |
1.8 |
|
489 |
|
|
It must return the next time to trigger, based on the passed |
490 |
root |
1.26 |
time value (that is, the lowest time value larger than or equal |
491 |
|
|
to to the second argument). It will usually be called just |
492 |
|
|
before the callback will be triggered, but might be called at |
493 |
|
|
other times, too. |
494 |
root |
1.8 |
|
495 |
|
|
This can be used to create very complex timers, such as a timer |
496 |
|
|
that triggers on each midnight, local time (actually 24 hours |
497 |
|
|
after the last midnight, to keep the example simple. If you know |
498 |
|
|
a way to do it correctly in about the same space (without |
499 |
|
|
requiring elaborate modules), drop me a note :): |
500 |
|
|
|
501 |
|
|
my $daily = EV::periodic 0, 0, sub { |
502 |
|
|
my ($w, $now) = @_; |
503 |
|
|
|
504 |
|
|
use Time::Local (); |
505 |
|
|
my (undef, undef, undef, $d, $m, $y) = localtime $now; |
506 |
|
|
86400 + Time::Local::timelocal 0, 0, 0, $d, $m, $y |
507 |
|
|
}, sub { |
508 |
|
|
print "it's midnight or likely shortly after, now\n"; |
509 |
|
|
}; |
510 |
root |
1.6 |
|
511 |
|
|
The "periodic_ns" variant doesn't start (activate) the newly created |
512 |
root |
1.2 |
watcher. |
513 |
|
|
|
514 |
root |
1.8 |
$w->set ($at, $interval, $reschedule_cb) |
515 |
root |
1.6 |
Reconfigures the watcher, see the constructor above for details. Can |
516 |
root |
1.13 |
be called at any time. |
517 |
root |
1.6 |
|
518 |
root |
1.8 |
$w->again |
519 |
|
|
Simply stops and starts the watcher again. |
520 |
|
|
|
521 |
root |
1.19 |
$time = $w->at |
522 |
|
|
Return the time that the watcher is expected to trigger next. |
523 |
|
|
|
524 |
root |
1.13 |
SIGNAL WATCHERS - signal me when a signal gets signalled! |
525 |
root |
1.6 |
$w = EV::signal $signal, $callback |
526 |
|
|
$w = EV::signal_ns $signal, $callback |
527 |
root |
1.4 |
Call the callback when $signal is received (the signal can be |
528 |
root |
1.13 |
specified by number or by name, just as with "kill" or %SIG). |
529 |
root |
1.4 |
|
530 |
|
|
EV will grab the signal for the process (the kernel only allows one |
531 |
root |
1.6 |
component to receive a signal at a time) when you start a signal |
532 |
|
|
watcher, and removes it again when you stop it. Perl does the same |
533 |
|
|
when you add/remove callbacks to %SIG, so watch out. |
534 |
|
|
|
535 |
|
|
You can have as many signal watchers per signal as you want. |
536 |
root |
1.1 |
|
537 |
root |
1.6 |
The "signal_ns" variant doesn't start (activate) the newly created |
538 |
|
|
watcher. |
539 |
|
|
|
540 |
|
|
$w->set ($signal) |
541 |
|
|
Reconfigures the watcher, see the constructor above for details. Can |
542 |
root |
1.13 |
be called at any time. |
543 |
root |
1.6 |
|
544 |
root |
1.7 |
$current_signum = $w->signal |
545 |
|
|
$old_signum = $w->signal ($new_signal) |
546 |
|
|
Returns the previously set signal (always as a number not name) and |
547 |
|
|
optionally set a new one. |
548 |
|
|
|
549 |
root |
1.13 |
CHILD WATCHERS - watch out for process status changes |
550 |
root |
1.22 |
$w = EV::child $pid, $trace, $callback |
551 |
|
|
$w = EV::child_ns $pid, $trace, $callback |
552 |
|
|
$w = $loop->child ($pid, $trace, $callback) |
553 |
|
|
$w = $loop->child_ns ($pid, $trace, $callback) |
554 |
root |
1.6 |
Call the callback when a status change for pid $pid (or any pid if |
555 |
root |
1.22 |
$pid is 0) has been received (a status change happens when the |
556 |
|
|
process terminates or is killed, or, when trace is true, |
557 |
|
|
additionally when it is stopped or continued). More precisely: when |
558 |
|
|
the process receives a "SIGCHLD", EV will fetch the outstanding |
559 |
|
|
exit/wait status for all changed/zombie children and call the |
560 |
|
|
callback. |
561 |
root |
1.6 |
|
562 |
root |
1.13 |
It is valid (and fully supported) to install a child watcher after a |
563 |
|
|
child has exited but before the event loop has started its next |
564 |
|
|
iteration (for example, first you "fork", then the new child process |
565 |
|
|
might exit, and only then do you install a child watcher in the |
566 |
|
|
parent for the new pid). |
567 |
root |
1.6 |
|
568 |
root |
1.13 |
You can access both exit (or tracing) status and pid by using the |
569 |
|
|
"rstatus" and "rpid" methods on the watcher object. |
570 |
|
|
|
571 |
|
|
You can have as many pid watchers per pid as you want, they will all |
572 |
|
|
be called. |
573 |
root |
1.6 |
|
574 |
|
|
The "child_ns" variant doesn't start (activate) the newly created |
575 |
|
|
watcher. |
576 |
root |
1.1 |
|
577 |
root |
1.22 |
$w->set ($pid, $trace) |
578 |
root |
1.6 |
Reconfigures the watcher, see the constructor above for details. Can |
579 |
root |
1.13 |
be called at any time. |
580 |
root |
1.6 |
|
581 |
root |
1.7 |
$current_pid = $w->pid |
582 |
|
|
Returns the previously set process id and optionally set a new one. |
583 |
|
|
|
584 |
|
|
$exit_status = $w->rstatus |
585 |
|
|
Return the exit/wait status (as returned by waitpid, see the waitpid |
586 |
|
|
entry in perlfunc). |
587 |
|
|
|
588 |
|
|
$pid = $w->rpid |
589 |
|
|
Return the pid of the awaited child (useful when you have installed |
590 |
|
|
a watcher for all pids). |
591 |
|
|
|
592 |
root |
1.13 |
STAT WATCHERS - did the file attributes just change? |
593 |
|
|
$w = EV::stat $path, $interval, $callback |
594 |
|
|
$w = EV::stat_ns $path, $interval, $callback |
595 |
root |
1.20 |
$w = $loop->stat ($path, $interval, $callback) |
596 |
|
|
$w = $loop->stat_ns ($path, $interval, $callback) |
597 |
root |
1.13 |
Call the callback when a file status change has been detected on |
598 |
|
|
$path. The $path does not need to exist, changing from "path exists" |
599 |
|
|
to "path does not exist" is a status change like any other. |
600 |
|
|
|
601 |
|
|
The $interval is a recommended polling interval for systems where |
602 |
|
|
OS-supported change notifications don't exist or are not supported. |
603 |
|
|
If you use 0 then an unspecified default is used (which is highly |
604 |
|
|
recommended!), which is to be expected to be around five seconds |
605 |
|
|
usually. |
606 |
|
|
|
607 |
|
|
This watcher type is not meant for massive numbers of stat watchers, |
608 |
|
|
as even with OS-supported change notifications, this can be |
609 |
|
|
resource-intensive. |
610 |
|
|
|
611 |
|
|
The "stat_ns" variant doesn't start (activate) the newly created |
612 |
|
|
watcher. |
613 |
|
|
|
614 |
root |
1.14 |
... = $w->stat |
615 |
|
|
This call is very similar to the perl "stat" built-in: It stats |
616 |
|
|
(using "lstat") the path specified in the watcher and sets perls |
617 |
|
|
stat cache (as well as EV's idea of the current stat values) to the |
618 |
|
|
values found. |
619 |
|
|
|
620 |
|
|
In scalar context, a boolean is return indicating success or failure |
621 |
|
|
of the stat. In list context, the same 13-value list as with stat is |
622 |
|
|
returned (except that the blksize and blocks fields are not |
623 |
|
|
reliable). |
624 |
|
|
|
625 |
|
|
In the case of an error, errno is set to "ENOENT" (regardless of the |
626 |
|
|
actual error value) and the "nlink" value is forced to zero (if the |
627 |
|
|
stat was successful then nlink is guaranteed to be non-zero). |
628 |
|
|
|
629 |
|
|
See also the next two entries for more info. |
630 |
|
|
|
631 |
|
|
... = $w->attr |
632 |
|
|
Just like "$w->stat", but without the initial stat'ing: this returns |
633 |
|
|
the values most recently detected by EV. See the next entry for more |
634 |
|
|
info. |
635 |
|
|
|
636 |
|
|
... = $w->prev |
637 |
|
|
Just like "$w->stat", but without the initial stat'ing: this returns |
638 |
|
|
the previous set of values, before the change. |
639 |
|
|
|
640 |
|
|
That is, when the watcher callback is invoked, "$w->prev" will be |
641 |
|
|
set to the values found *before* a change was detected, while |
642 |
|
|
"$w->attr" returns the values found leading to the change detection. |
643 |
|
|
The difference (if any) between "prev" and "attr" is what triggered |
644 |
|
|
the callback. |
645 |
|
|
|
646 |
|
|
If you did something to the filesystem object and do not want to |
647 |
|
|
trigger yet another change, you can call "stat" to update EV's idea |
648 |
|
|
of what the current attributes are. |
649 |
|
|
|
650 |
root |
1.13 |
$w->set ($path, $interval) |
651 |
|
|
Reconfigures the watcher, see the constructor above for details. Can |
652 |
|
|
be called at any time. |
653 |
|
|
|
654 |
|
|
$current_path = $w->path |
655 |
|
|
$old_path = $w->path ($new_path) |
656 |
|
|
Returns the previously set path and optionally set a new one. |
657 |
|
|
|
658 |
|
|
$current_interval = $w->interval |
659 |
|
|
$old_interval = $w->interval ($new_interval) |
660 |
|
|
Returns the previously set interval and optionally set a new one. |
661 |
|
|
Can be used to query the actual interval used. |
662 |
|
|
|
663 |
|
|
IDLE WATCHERS - when you've got nothing better to do... |
664 |
root |
1.6 |
$w = EV::idle $callback |
665 |
|
|
$w = EV::idle_ns $callback |
666 |
root |
1.20 |
$w = $loop->idle ($callback) |
667 |
|
|
$w = $loop->idle_ns ($callback) |
668 |
root |
1.16 |
Call the callback when there are no other pending watchers of the |
669 |
|
|
same or higher priority (excluding check, prepare and other idle |
670 |
|
|
watchers of the same or lower priority, of course). They are called |
671 |
|
|
idle watchers because when the watcher is the highest priority |
672 |
|
|
pending event in the process, the process is considered to be idle |
673 |
|
|
at that priority. |
674 |
|
|
|
675 |
|
|
If you want a watcher that is only ever called when *no* other |
676 |
|
|
events are outstanding you have to set the priority to "EV::MINPRI". |
677 |
root |
1.1 |
|
678 |
root |
1.6 |
The process will not block as long as any idle watchers are active, |
679 |
|
|
and they will be called repeatedly until stopped. |
680 |
root |
1.1 |
|
681 |
root |
1.16 |
For example, if you have idle watchers at priority 0 and 1, and an |
682 |
|
|
I/O watcher at priority 0, then the idle watcher at priority 1 and |
683 |
|
|
the I/O watcher will always run when ready. Only when the idle |
684 |
|
|
watcher at priority 1 is stopped and the I/O watcher at priority 0 |
685 |
|
|
is not pending with the 0-priority idle watcher be invoked. |
686 |
|
|
|
687 |
root |
1.6 |
The "idle_ns" variant doesn't start (activate) the newly created |
688 |
|
|
watcher. |
689 |
root |
1.4 |
|
690 |
root |
1.13 |
PREPARE WATCHERS - customise your event loop! |
691 |
root |
1.6 |
$w = EV::prepare $callback |
692 |
|
|
$w = EV::prepare_ns $callback |
693 |
root |
1.20 |
$w = $loop->prepare ($callback) |
694 |
|
|
$w = $loop->prepare_ns ($callback) |
695 |
root |
1.6 |
Call the callback just before the process would block. You can still |
696 |
|
|
create/modify any watchers at this point. |
697 |
root |
1.1 |
|
698 |
root |
1.6 |
See the EV::check watcher, below, for explanations and an example. |
699 |
root |
1.1 |
|
700 |
root |
1.6 |
The "prepare_ns" variant doesn't start (activate) the newly created |
701 |
|
|
watcher. |
702 |
root |
1.1 |
|
703 |
root |
1.13 |
CHECK WATCHERS - customise your event loop even more! |
704 |
root |
1.6 |
$w = EV::check $callback |
705 |
|
|
$w = EV::check_ns $callback |
706 |
root |
1.20 |
$w = $loop->check ($callback) |
707 |
|
|
$w = $loop->check_ns ($callback) |
708 |
root |
1.6 |
Call the callback just after the process wakes up again (after it |
709 |
|
|
has gathered events), but before any other callbacks have been |
710 |
|
|
invoked. |
711 |
|
|
|
712 |
|
|
This is used to integrate other event-based software into the EV |
713 |
|
|
mainloop: You register a prepare callback and in there, you create |
714 |
|
|
io and timer watchers as required by the other software. Here is a |
715 |
|
|
real-world example of integrating Net::SNMP (with some details left |
716 |
|
|
out): |
717 |
|
|
|
718 |
|
|
our @snmp_watcher; |
719 |
|
|
|
720 |
|
|
our $snmp_prepare = EV::prepare sub { |
721 |
|
|
# do nothing unless active |
722 |
|
|
$dispatcher->{_event_queue_h} |
723 |
|
|
or return; |
724 |
|
|
|
725 |
|
|
# make the dispatcher handle any outstanding stuff |
726 |
root |
1.12 |
... not shown |
727 |
root |
1.6 |
|
728 |
root |
1.16 |
# create an I/O watcher for each and every socket |
729 |
root |
1.6 |
@snmp_watcher = ( |
730 |
|
|
(map { EV::io $_, EV::READ, sub { } } |
731 |
|
|
keys %{ $dispatcher->{_descriptors} }), |
732 |
root |
1.12 |
|
733 |
|
|
EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE] |
734 |
|
|
? $event->[Net::SNMP::Dispatcher::_TIME] - EV::now : 0), |
735 |
|
|
0, sub { }, |
736 |
root |
1.6 |
); |
737 |
|
|
}; |
738 |
|
|
|
739 |
root |
1.12 |
The callbacks are irrelevant (and are not even being called), the |
740 |
|
|
only purpose of those watchers is to wake up the process as soon as |
741 |
|
|
one of those events occurs (socket readable, or timer timed out). |
742 |
|
|
The corresponding EV::check watcher will then clean up: |
743 |
root |
1.6 |
|
744 |
|
|
our $snmp_check = EV::check sub { |
745 |
|
|
# destroy all watchers |
746 |
|
|
@snmp_watcher = (); |
747 |
|
|
|
748 |
|
|
# make the dispatcher handle any new stuff |
749 |
root |
1.12 |
... not shown |
750 |
root |
1.6 |
}; |
751 |
|
|
|
752 |
|
|
The callbacks of the created watchers will not be called as the |
753 |
root |
1.31 |
watchers are destroyed before this can happen (remember EV::check |
754 |
root |
1.6 |
gets called first). |
755 |
root |
1.1 |
|
756 |
root |
1.6 |
The "check_ns" variant doesn't start (activate) the newly created |
757 |
|
|
watcher. |
758 |
root |
1.1 |
|
759 |
root |
1.13 |
FORK WATCHERS - the audacity to resume the event loop after a fork |
760 |
|
|
Fork watchers are called when a "fork ()" was detected. The invocation |
761 |
|
|
is done before the event loop blocks next and before "check" watchers |
762 |
|
|
are being called, and only in the child after the fork. |
763 |
|
|
|
764 |
|
|
$w = EV::fork $callback |
765 |
|
|
$w = EV::fork_ns $callback |
766 |
root |
1.20 |
$w = $loop->fork ($callback) |
767 |
|
|
$w = $loop->fork_ns ($callback) |
768 |
root |
1.13 |
Call the callback before the event loop is resumed in the child |
769 |
|
|
process after a fork. |
770 |
|
|
|
771 |
|
|
The "fork_ns" variant doesn't start (activate) the newly created |
772 |
|
|
watcher. |
773 |
|
|
|
774 |
root |
1.21 |
EMBED WATCHERS - when one backend isn't enough... |
775 |
|
|
This is a rather advanced watcher type that lets you embed one event |
776 |
|
|
loop into another (currently only IO events are supported in the |
777 |
|
|
embedded loop, other types of watchers might be handled in a delayed or |
778 |
|
|
incorrect fashion and must not be used). |
779 |
|
|
|
780 |
|
|
See the libev documentation at |
781 |
|
|
<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#code_ev_embed_code |
782 |
root |
1.30 |
_when_one_backend_> (locally installed as EV::libev) for more details. |
783 |
root |
1.21 |
|
784 |
|
|
In short, this watcher is most useful on BSD systems without working |
785 |
|
|
kqueue to still be able to handle a large number of sockets: |
786 |
|
|
|
787 |
root |
1.28 |
my $socket_loop; |
788 |
|
|
|
789 |
|
|
# check wether we use SELECT or POLL _and_ KQUEUE is supported |
790 |
|
|
if ( |
791 |
|
|
(EV::backend & (EV::BACKEND_POLL | EV::BACKEND_SELECT)) |
792 |
|
|
&& (EV::supported_backends & EV::embeddable_backends & EV::BACKEND_KQUEUE) |
793 |
|
|
) { |
794 |
|
|
# use kqueue for sockets |
795 |
|
|
$socket_loop = new EV::Loop EV::BACKEND_KQUEUE | EV::FLAG_NOENV; |
796 |
|
|
} |
797 |
|
|
|
798 |
|
|
# use the default loop otherwise |
799 |
|
|
$socket_loop ||= EV::default_loop; |
800 |
root |
1.21 |
|
801 |
root |
1.29 |
$w = EV::embed $otherloop[, $callback] |
802 |
|
|
$w = EV::embed_ns $otherloop[, $callback] |
803 |
|
|
$w = $loop->embed ($otherloop[, $callback]) |
804 |
|
|
$w = $loop->embed_ns ($otherloop[, $callback]) |
805 |
root |
1.21 |
Call the callback when the embedded event loop ($otherloop) has any |
806 |
root |
1.29 |
I/O activity. The $callback is optional: if it is missing, then the |
807 |
|
|
embedded event loop will be managed automatically (which is |
808 |
|
|
recommended), otherwise you have to invoke "sweep" yourself. |
809 |
root |
1.21 |
|
810 |
|
|
The "embed_ns" variant doesn't start (activate) the newly created |
811 |
|
|
watcher. |
812 |
|
|
|
813 |
root |
1.23 |
ASYNC WATCHERS - how to wake up another event loop |
814 |
|
|
Async watchers are provided by EV, but have little use in perl directly, |
815 |
|
|
as perl neither supports threads nor direct access to signal handlers or |
816 |
|
|
other contexts where they could be of value. |
817 |
|
|
|
818 |
|
|
It is, however, possible to use them from the XS level. |
819 |
|
|
|
820 |
|
|
Please see the libev documentation for further details. |
821 |
|
|
|
822 |
root |
1.24 |
$w = EV::async $callback |
823 |
|
|
$w = EV::async_ns $callback |
824 |
|
|
$w->send |
825 |
|
|
$bool = $w->async_pending |
826 |
|
|
|
827 |
root |
1.16 |
PERL SIGNALS |
828 |
|
|
While Perl signal handling (%SIG) is not affected by EV, the behaviour |
829 |
|
|
with EV is as the same as any other C library: Perl-signals will only be |
830 |
|
|
handled when Perl runs, which means your signal handler might be invoked |
831 |
|
|
only the next time an event callback is invoked. |
832 |
|
|
|
833 |
|
|
The solution is to use EV signal watchers (see "EV::signal"), which will |
834 |
|
|
ensure proper operations with regards to other event watchers. |
835 |
|
|
|
836 |
|
|
If you cannot do this for whatever reason, you can also force a watcher |
837 |
|
|
to be called on every event loop iteration by installing a "EV::check" |
838 |
|
|
watcher: |
839 |
|
|
|
840 |
|
|
my $async_check = EV::check sub { }; |
841 |
|
|
|
842 |
root |
1.20 |
This ensures that perl gets into control for a short time to handle any |
843 |
|
|
pending signals, and also ensures (slightly) slower overall operation. |
844 |
root |
1.16 |
|
845 |
root |
1.5 |
THREADS |
846 |
root |
1.12 |
Threads are not supported by this module in any way. Perl pseudo-threads |
847 |
|
|
is evil stuff and must die. As soon as Perl gains real threads I will |
848 |
|
|
work on thread support for it. |
849 |
|
|
|
850 |
|
|
FORK |
851 |
|
|
Most of the "improved" event delivering mechanisms of modern operating |
852 |
|
|
systems have quite a few problems with fork(2) (to put it bluntly: it is |
853 |
|
|
not supported and usually destructive). Libev makes it possible to work |
854 |
|
|
around this by having a function that recreates the kernel state after |
855 |
|
|
fork in the child. |
856 |
|
|
|
857 |
|
|
On non-win32 platforms, this module requires the pthread_atfork |
858 |
|
|
functionality to do this automatically for you. This function is quite |
859 |
|
|
buggy on most BSDs, though, so YMMV. The overhead for this is quite |
860 |
|
|
negligible, because everything the function currently does is set a flag |
861 |
|
|
that is checked only when the event loop gets used the next time, so |
862 |
|
|
when you do fork but not use EV, the overhead is minimal. |
863 |
|
|
|
864 |
|
|
On win32, there is no notion of fork so all this doesn't apply, of |
865 |
|
|
course. |
866 |
root |
1.2 |
|
867 |
|
|
SEE ALSO |
868 |
root |
1.20 |
EV::ADNS (asynchronous DNS), Glib::EV (makes Glib/Gtk2 use EV as event |
869 |
|
|
loop), EV::Glib (embed Glib into EV), Coro::EV (efficient coroutines |
870 |
root |
1.25 |
with EV), Net::SNMP::EV (asynchronous SNMP), AnyEvent for event-loop |
871 |
|
|
agnostic and portable event driven programming. |
872 |
root |
1.1 |
|
873 |
|
|
AUTHOR |
874 |
root |
1.28 |
Marc Lehmann <schmorp@schmorp.de> |
875 |
|
|
http://home.schmorp.de/ |
876 |
root |
1.1 |
|