nginx-0.4.14

[Jonathan]

On Nov 29, 2006, at 4:00 PM, Igor Sysoev wrote:

> No, there was no changes in these area.
> Have you changed configuration files after upgrade ?

no.  same exact configuration.  there was nothing in the documents to  
suggest a need to upgrade.

> The master process creates the directories for temporary files
> and does chown() and chmod() to allow unpriviliged workers to  
> create files.
the master process was failing on that though, because there was no "/ 
var/tmp/nginx/proxy_temp"

nginx would have had to support some sort of "mkdir -p" in creating  
the "var/tmp/nginx/proxy_temp/1" directory.
maybe there should be a check for it in startup?

i can't explain why this error just happened out of nowhere.

the content that causes the errors has been the same- it hasn't  
changed - it was the same 44 and 50 k files (happens on dynamic  
content too, but i can guarantee that those 2 files didn't change).   
before upgrading my nginx , everything served fine.

if nginx were buffering to a tmp file on the earlier releases, a /var/ 
tmp/nginx/proxy_temp directory should have existed - and this issue  
would not have come up.  so i just assumed something happened to the  
proxy_buffers / proxy_buffer_size code.








// Jonathan Vanasco

| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -
| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -
| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -