Re: releasing memory.

My module has c++ code which instantiates a class. I am driving most of my c++ from one ptr which I am saving in the context. I tried changing my code to use pool cleanup, it behaving worse than request->cleanup. Of the four requests I send, the cleanup handler is only getting called for two. I

Re: Http: make ngx_http_init_listening a public api

Thank you for your reply. As a client oriented proxy server, nginx will boot several worker process to listen on the same port. If a tcp connection is initiated, this connection will be processed by one worker. This model is simple yet efficient. However this model makes it impossible to let

RE: [PATCH] Proxy: support configuration of socket buffer sizes

Greetings, I just wanted to follow up on this patch and make sure that the fraud detection notice or confidentiality notice added by my company wasn't precluding it from consideration. Thanks! Nate -Original Message- From: nginx-devel [mailto:nginx-devel-boun...@nginx.org] On Behalf

Re: releasing memory.

Hello! On Thu, May 18, 2017 at 10:23:18AM -0700, Dk Jack wrote: > I just want to release memory l've allocated. One more question, > is the context memory automatically removed or is the module > responsible for freeing it. Anything you allocate from request pool (r->pool) using

Re: Http: make ngx_http_init_listening a public api

Hello! On Fri, May 19, 2017 at 01:12:29AM +0800, 0...@lvht.net wrote: > Is there any maintainer who could review this patch? Thanks. I don't think this change is needed. Listening sockets are to be created using the "listen" directive of the core module, they are not expected to be added by

Re: releasing memory.

Thank you Maxim, I just want to release memory l've allocated. One more question, is the context memory automatically removed or is the module responsible for freeing it. > On May 18, 2017, at 6:32 AM, Maxim Dounin wrote: > > Hello! > >> On Wed, May 17, 2017 at

Re: Http: make ngx_http_init_listening a public api

Hello, Is there any maintainer who could review this patch? Thanks. > 在 2017年5月1日，08:31，nginx-devel-boun...@nginx.org 写道： > > # HG changeset patch > # User 吕海涛 <0...@lvht.net> > # Date 1493595577 -28800 > # Mon May 01 07:39:37 2017 +0800 > # Node ID 2ddd0894c1a6c7efe45310b874a5b4091b58bb81

[nginx] Cache: ignore long locked entries during forced expire.

details: http://hg.nginx.org/nginx/rev/ab199f0eb8e8 branches: changeset: 7002:ab199f0eb8e8 user: Dmitry Volyntsev date: Thu May 18 18:39:16 2017 +0300 description: Cache: ignore long locked entries during forced expire. Abnormally exited workers may leave locked

Re: releasing memory.

Hello! On Wed, May 17, 2017 at 05:53:40PM -0700, Dk Jack wrote: > Hi, > In my module, I registered a NGX_HTTP_POST_READ_PHASE handler. When this > handler is invoked, I allocate my module context and attach it to the > request. I also allocate some other memory and save the pointers to that >

[nginx] Upstream: fixed u->headers_in.headers allocation error handling.

details: http://hg.nginx.org/nginx/rev/08537eab4f23 branches: changeset: 7001:08537eab4f23 user: Sergey Kandaurov date: Thu May 18 14:17:00 2017 +0300 description: Upstream: fixed u->headers_in.headers allocation error handling. Previously, an allocation error