Welcome! Log In Create A New Profile

Advanced

Re: RFC on C Library Safety in Nginx Module Callback

Sinan Kaya
June 14, 2019 02:36PM
On 6/14/2019 8:51 AM, Ranier Vf wrote:
> Maybe this help.
> http://www.doublersolutions.com/docs/dce/osfdocs/htmls/develop/appdev/Appde193.htm
>
> "One solution to the problem of calling *fork( )* in a multithreaded
> environment exists. (Note that this method will not work for server
> application code or any other application code that is invoked by a
> callback from a library.) Before an application performs a *fork( )*
> followed by something other than *exec( )*, it must cancel all of the
> other threads. After it joins the canceled threads, it can safely *fork(
> )* because it is the only thread in existence. This means that libraries
> that create threads must establish cancel handlers that propagate the
> cancel to the created threads and join them. The application should save
> enough state so that the threads can be recreated and restarted after
> the *fork( )* processing completes. "

Yes, this helps. As long as nginx has been designed to honor these
rules, we can make our application do the same thing.

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

RFC on C Library Safety in Nginx Module Callback

Sinan Kaya 140 June 13, 2019 09:10PM

Re: RFC on C Library Safety in Nginx Module Callback

Ranier Vf 55 June 14, 2019 08:52AM

Re: RFC on C Library Safety in Nginx Module Callback

Sinan Kaya 53 June 14, 2019 02:36PM

Re: RFC on C Library Safety in Nginx Module Callback

Maxim Dounin 56 June 17, 2019 09:08AM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 71
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready