Hi Gabriel,

I don't mind so much that Apache/mod_fcgid buffers the entire input, but even 
after the upload has completed and the input has been passed to the fastcgi 
application, Apache has still not freed the memory.  Subsequent uploads just 
keep adding to the overall Apache memory usage.

Unfortunately in my situation, I cannot simply tell the system not to use 
fastcgi for upload scripts as the system is used to host PHP sites for 
customers.  I guess my only option at this stage is to limit Apache memory 
using ulimit.

--- On Thu, 5/6/08, Gabriel Barazer <[EMAIL PROTECTED]> wrote:

> From: Gabriel Barazer <[EMAIL PROTECTED]>
> Subject: Re: [Mod-fcgid-users] Apache consuming all available memory
> To: [EMAIL PROTECTED], mod-fcgid-users@lists.sourceforge.net
> Date: Thursday, 5 June, 2008, 3:05 AM
> Hi,
> I have reported that problem about a year ago and yes, this
> is still not 
> fixed. Essentially this is because the fix needs _a lot_ of
> changes in 
> the module core functions, because the whole logic has to
> be rewritten. 
> In the current code, mod_fcgid buffers the entire input
> data before 
> testing the input size (which makes MaxRequestLen useless)
> and no data 
> can be transmitted to the fastcgi process because it
> doesn't even exist 
> yet (the process spawning logic is done after the input
> data is 
> buffered). Even though the fastcgi process would already
> exist, the 
> input request is not bridged to it before the buffering
> step (meaning: 
> you cannot avoid the big memory buffering in any way).

Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html

Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
Mod-fcgid-users mailing list

Reply via email to