>Number: 3565 >Category: general >Synopsis: When apache spawns a child process, it doesn't exit it cleanly. >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sat Dec 19 10:10:00 PST 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.2.5, 1.2.6, 1.3.3 >Environment: FreeBSD nz.negativezero.com 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Wed Jul 29 12:33:02 CDT 1998 [EMAIL PROTECTED]:/usr/src/sys/compile/NZ i386 FreeBSD nz2.negativezero.com 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Sat Aug 1 11:10:29 CDT 1998 [EMAIL PROTECTED]:/usr/src/sys/compile/NZ2 i386 >Description: It appears that when apache spawns a child process, once that process is finished it doesn't exit correctly. We have had this problem on two servers both running apache. We have raised the max processes per user multiple times on the machines and the error simply takes longer to reoccur, but it does reoccur at some point. The only way to release the processes started is to SIGHUP httpd. I have noticed in the bug report database, that there are many people saying that it is the load the sets it off, but I believe that apache isn't releasing the processes correctly as suggested by someone in bug report #83. >How-To-Repeat:
>Fix: >Audit-Trail: >Unformatted: [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! ]
