From 756a6378f76a80c595335d4a78ab426cc44d247d Mon Sep 17 00:00:00 2001 From: root Date: Thu, 29 Nov 2007 17:28:13 +0000 Subject: implement EVFLAG_FORKCHECK --- ev.pod | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 'ev.pod') diff --git a/ev.pod b/ev.pod index 1e0234c..b1a5fe5 100644 --- a/ev.pod +++ b/ev.pod @@ -268,6 +268,26 @@ override the flags completely if it is found in the environment. This is useful to try out specific backends to test their performance, or to work around bugs. +=item C + +Instead of calling C or C manually after +a fork, you can also make libev check for a fork in each iteration by +enabling this flag. + +This works by calling C on every iteration of the loop, +and thus this might slow down your event loop if you do a lot of loop +iterations and little real work, but is usually not noticable (on my +Linux system for example, C is actually a simple 5-insn sequence +without a syscall and thus I fast, but my Linux system also has +C which is even faster). + +The big advantage of this flag is that you can forget about fork (and +forget about forgetting to tell libev about forking) when you use this +flag. + +This flag setting cannot be overriden or specified in the C +environment variable. + =item C (value 1, portable select backend) This is your standard select(2) backend. Not I standard, as -- cgit v1.2.3