Nginx-0.7.32


#1

Changes with nginx 0.7.32 26 Jan
2009

*) Feature: now a directory existence testing can be set explicitly 

in
the “try_files” directive.

*) Bugfix: fastcgi_store stored files not always.

*) Bugfix: in geo ranges.

*) Bugfix: in shared memory allocations if nginx was built without
   debugging.
   Thanks to Andrey Kvasov.

#2

Grab the Nginx 0.7.32 Windows release here:
http://www.kevinworthington.com/2009/01/26/nginx-0732-for-windows-win32/

Thanks,
Kevin

Kevin W.


#3

What do you mean by “in shared memory allocations if nginx was built
without debugging” can you please elaborate on this?


#4

On Mon, Jan 26, 2009 at 12:34 PM, Victor I. removed_email_address@domain.invalid
wrote:

What do you mean by “in shared memory allocations if nginx was built
without debugging” can you please elaborate on this?

I hoped this fixed an issue on Windows, but nope: the Virtual Size of
the nginx process is over 400Mb - see
http://forum.sysinternals.com/forum_posts.asp?TID=17603

Dan


#5

On Mon, Jan 26, 2009 at 08:14:49PM -0800, Dan Dascalescu wrote:

On Mon, Jan 26, 2009 at 12:34 PM, Victor I. removed_email_address@domain.invalid wrote:

What do you mean by “in shared memory allocations if nginx was built
without debugging” can you please elaborate on this?

I hoped this fixed an issue on Windows, but nope: the Virtual Size of
the nginx process is over 400Mb - see
http://forum.sysinternals.com/forum_posts.asp?TID=17603

No, this is another issue. Probably it may be assosiated with Cygwin
library.


#6

On Mon, Jan 26, 2009 at 09:34:20PM +0100, Victor I. wrote:

What do you mean by “in shared memory allocations if nginx was built
without debugging” can you please elaborate on this?

It should mean “in [ big (half page and more) ] shared memory
allocations
if nginx was built without debugging”.

If nginx was built without “–with-debug” option, then these shared
memory allocations crashed a shared pool. Currently the pools are used
in ssl, limit_zone and limit_req modules.