Lines Matching refs:after
364 C<SIGCHLD> signal handler I<after> calling C<ev_default_init>.
410 Instead of calling C<ev_loop_fork> manually after a fork, you can also
569 only for sockets (after having made sure that sockets work with kqueue on
691 sense after forking, in the child process. You I<must> call it (or use
697 Again, you I<have> to call it on I<any> loop that you want to re-use after
710 it just in case after a fork.
808 after you have initialised all your watchers and you want to start
835 block your process in case there are no events and will return after one
843 user-registered callback will be called), and will return after one
900 Can be used to make a call to C<ev_run> return early (but only after it
920 returning. In such a case, call C<ev_unref> after starting, and C<ev_ref>
927 third-party libraries. Just remember to I<unref after start> and I<ref
1048 C<release> and C<acquire> (that's their only purpose after all), no
1189 just after C<ev_run> has gathered them, but before it queues any callbacks
1206 The event loop has been resumed in the child process after fork (see
1684 ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to
1707 the next iteration again (the connection still exists after all), and
1782 Timer watchers are simple relative timers that generate an event after a
1783 given time, and optionally repeating in regular intervals after that.
1786 times out after an hour and you reset your system clock to January last
1787 year, it will still time out after (roughly) one hour. "Roughly" because
1791 The callback is guaranteed to be invoked only I<after> its timeout has
1803 you want to raise some error after a while.
1846 C<after> argument to C<ev_timer_set>, and only ever use the C<repeat>
1890 ev_tstamp after = last_activity - ev_now (EV_A) + timeout;
1893 if (after < 0.)
1901 // after "after" seconds, which is the earliest time
1903 ev_timer_set (w, after, 0.);
1985 off after the first million or so of active timers, i.e. it's usually
1990 If you ask a timer to call your callback after three seconds, then
1991 you expect it to be invoked after three seconds - but of course, this
1996 So, libev tries to invoke your callback as soon as possible I<after> the
2011 501" and invoke the callback 0.1s after it was started, even though a
2018 the callback at system time 502, or 1.1s after the timer was started.
2029 time only before and after C<ev_run> collects new events, which causes a
2040 ev_timer_set (&timer, after + (ev_time () - ev_now ()), 0.);
2073 connection after 100 seconds") then this shouldn't bother you as it is
2114 =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)
2116 =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)
2118 Configure the timer to trigger after C<after> seconds. If C<repeat>
2160 That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns
2176 Example: Create a timer that fires after 60 seconds.
2188 Example: Create a timeout timer that times out after 10 seconds of
2219 You can tell a periodic watcher to trigger after some specific point
2224 C<ev_timer>, which would still trigger roughly 10 seconds after starting
2253 In this configuration the watcher triggers an event after the wall clock
2327 next midnight after C<now> and return the timestamp value for this. How
2424 Only after the first watcher for a signal is started will libev actually
2437 (C<sigaction>) are unspecified after starting a signal watcher (and after
2514 exits). It is permissible to install a child watcher I<after> the child
2532 first child watcher is started after the child exits. The occurrence
2542 C<SIGCHLD> after initialising the default loop, and making sure the
2623 happen after the watcher has been started will be reported.
2723 than a second (or till slightly after the next full second boundary), using
2826 /* now it's one second after the most recent passwd change */
2860 "pseudo-background processing", or delay processing stuff to after the
2954 any other watchers after the poll (this doesn't matter for C<ev_prepare>
3047 // stop all watchers after blocking
3262 =head2 C<ev_fork> - the audacity to resume the event loop after a fork
3268 after the fork. If whoever good citizen calling C<ev_default_fork> cheats
3272 =head3 The special problem of life after fork - how is it possible?
3279 in the child, or both parent in child, in effect "continuing" after the
3535 started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and
3667 might want to do something to the request after starting it, such as
3717 // exit main program, after modal loop is finished
4012 (preferably after implementing it).