You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Graham Leggett <gr...@vwv.com> on 1998/11/18 09:39:14 UTC

mod_cgi/3414: Impossible to spawn a child process in the background from a CGI

>Number:         3414
>Category:       mod_cgi
>Synopsis:       Impossible to spawn a child process in the background from a CGI
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Nov 18 00:40:00 PST 1998
>Last-Modified:
>Originator:     graham@vwv.com
>Organization:
apache
>Release:        v1.3.3
>Environment:
Solaris v2.5.1
>Description:
While trying to trigger a subprocess that takes two hours to complete from a 
CGI program in C, it was discovered that as soon as the parent CGI process
exits having forked the subprocess as a child, Apache kills the child, and
thus the two hour subprocess.

This seems to be done to prevent runaway CGIs, however there does not seem
to be a configurable workaround for this should this functionality be needed.
>How-To-Repeat:

>Fix:
Provide a configurable workaround on a per script or per directory basis
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> 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!         ]