From 1ad1e600c3eebe009db39a0f9750ed4adb078857 Mon Sep 17 00:00:00 2001 From: root Date: Fri, 23 Nov 2007 04:36:03 +0000 Subject: *** empty log message *** --- ev.3 | 8 ++++---- ev.html | 8 ++++---- ev.pod | 6 +++--- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/ev.3 b/ev.3 index ab5e004..5fda031 100644 --- a/ev.3 +++ b/ev.3 @@ -129,7 +129,7 @@ .\" ======================================================================== .\" .IX Title """ 1" -.TH "" 1 "2007-11-22" "perl v5.8.8" "User Contributed Perl Documentation" +.TH "" 1 "2007-11-23" "perl v5.8.8" "User Contributed Perl Documentation" .SH "NAME" libev \- a high performance full\-featured event loop written in C .SH "SYNOPSIS" @@ -349,9 +349,9 @@ one. Despite the name, you can call it anytime, but it makes most sense after forking, in either the parent or child process (or both, but that again makes little sense). .Sp -You \fImust\fR call this function after forking if and only if you want to -use the event library in both processes. If you just fork+exec, you don't -have to call it. +You \fImust\fR call this function in the child process after forking if and +only if you want to use the event library in both processes. If you just +fork+exec, you don't have to call it. .Sp The function itself is quite fast and it's usually not a problem to call it just in case after a fork. To make this easy, the function will fit in diff --git a/ev.html b/ev.html index 437179a..fbfaeea 100644 --- a/ev.html +++ b/ev.html @@ -6,7 +6,7 @@ - + @@ -274,9 +274,9 @@ earlier call to ev_loop_new.

one. Despite the name, you can call it anytime, but it makes most sense after forking, in either the parent or child process (or both, but that again makes little sense).

You must call this function after forking if and only if you want to -use the event library in both processes. If you just fork+exec, you don't -have to call it.

You must call this function in the child process after forking if and +only if you want to use the event library in both processes. If you just +fork+exec, you don't have to call it.

The function itself is quite fast and it's usually not a problem to call it just in case after a fork. To make this easy, the function will fit in quite nicely into a call to pthread_atfork:

diff --git a/ev.pod b/ev.pod index 9845aff..30c164a 100644 --- a/ev.pod +++ b/ev.pod @@ -236,9 +236,9 @@ one. Despite the name, you can call it anytime, but it makes most sense after forking, in either the parent or child process (or both, but that again makes little sense). -You I call this function after forking if and only if you want to -use the event library in both processes. If you just fork+exec, you don't -have to call it. +You I call this function in the child process after forking if and +only if you want to use the event library in both processes. If you just +fork+exec, you don't have to call it. The function itself is quite fast and it's usually not a problem to call it just in case after a fork. To make this easy, the function will fit in -- cgit v1.2.3