Re: [PATCH]Valgind: a complaint about uninitialized bytes in epoll_data_t

Hello! On Tue, Jul 02, 2013 at 02:00:40AM +0900, cubicdaiya wrote: > Hello! > > In Debian squeeze 32bit, > Valgrind outputs the following message to nginx. > > ==17124== Syscall param epoll_ctl(event) points to uninitialised byte(s) > ==17124==at 0x418F9CE: epoll_ctl (syscall-template.S:82)

[PATCH]Valgind: a complaint about uninitialized bytes in epoll_data_t

Hello! In Debian squeeze 32bit, Valgrind outputs the following message to nginx. ==17124== Syscall param epoll_ctl(event) points to uninitialised byte(s) ==17124==at 0x418F9CE: epoll_ctl (syscall-template.S:82) ==17124==by 0x805FB35: ngx_event_process_init (ngx_event.c:853) ==17124==b

ngx_http_limit_conn_module feature request

Would it be possible to get a feature added to this module? What I would like is a variable containing the name of the zone of the rule that is responsible for the 503 error. Would be great for where there are limits on many factors. ___ nginx-devel mail

Re: Help with shared memory usage

Hello! On Fri, Jun 28, 2013 at 10:36:39PM -0300, Wandenberg Peixoto wrote: > Hi, > > I'm trying to understand how the shared memory pool works inside the Nginx. > To do that, I made a very small module which create a shared memory zone > with 2097152 bytes, > and allocating and freeing blocks of