ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.3
(Generate patch)

Comparing libev/ev.3 (file contents):
Revision 1.4 by root, Thu Nov 22 12:28:35 2007 UTC vs.
Revision 1.5 by root, Fri Nov 23 04:36:03 2007 UTC

127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title ""<STANDARD INPUT>" 1" 131.IX Title ""<STANDARD INPUT>" 1"
132.TH "<STANDARD INPUT>" 1 "2007-11-22" "perl v5.8.8" "User Contributed Perl Documentation" 132.TH "<STANDARD INPUT>" 1 "2007-11-23" "perl v5.8.8" "User Contributed Perl Documentation"
133.SH "NAME" 133.SH "NAME"
134libev \- a high performance full\-featured event loop written in C 134libev \- a high performance full\-featured event loop written in C
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 1 137.Vb 1
347This function reinitialises the kernel state for backends that have 347This function reinitialises the kernel state for backends that have
348one. Despite the name, you can call it anytime, but it makes most sense 348one. Despite the name, you can call it anytime, but it makes most sense
349after forking, in either the parent or child process (or both, but that 349after forking, in either the parent or child process (or both, but that
350again makes little sense). 350again makes little sense).
351.Sp 351.Sp
352You \fImust\fR call this function after forking if and only if you want to 352You \fImust\fR call this function in the child process after forking if and
353use the event library in both processes. If you just fork+exec, you don't 353only if you want to use the event library in both processes. If you just
354have to call it. 354fork+exec, you don't have to call it.
355.Sp 355.Sp
356The function itself is quite fast and it's usually not a problem to call 356The function itself is quite fast and it's usually not a problem to call
357it just in case after a fork. To make this easy, the function will fit in 357it just in case after a fork. To make this easy, the function will fit in
358quite nicely into a call to \f(CW\*(C`pthread_atfork\*(C'\fR: 358quite nicely into a call to \f(CW\*(C`pthread_atfork\*(C'\fR:
359.Sp 359.Sp

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines