The following reply was made to PR mod_cgi/3602; it has been noted by GNATS.
From: Mario Truyens <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: mod_cgi/3602: Not enough space: couldn't spawn child process Date: Wed, 3 Feb 1999 15:58:10 +0100 (MET) > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > [If you do not include this Cc, your reply may be ig- ] > [nored unless you are responding to an explicit request ] > [from a developer. ] > [Reply only with text; DO NOT SEND ATTACHMENTS! ] > > > Synopsis: Not enough space: couldn't spawn child process > > State-Changed-From-To: open-feedback > State-Changed-By: jim > State-Changed-When: Fri Jan 1 09:43:12 PST 1999 > State-Changed-Why: > Does it have enough swap space? How about the process table > (or other OS table) sizes? Are they big enough? Sounds like > one of the two is the problem. > OK, found the problem. Apache reserves a lot of memory without using is. This reserved memory is never shown unless you type 'swap -s'. This shows apache allocated all physical RAM and swap space (+300MB). Stopping Apache frees the memory and when Apache starts again, it begins eating memory. Why? Mario
