X-Git-Url: https://git.llucax.com/software/libev.git/blobdiff_plain/54a57c74105dc818388cec05e6fc874cdbfebf7f..cff78812ebbcab7601919f479447150fb7c2c9f4:/ev.html 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: