You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Viktor Bodrogi <vi...@nexus.hu> on 1999/01/22 23:20:48 UTC
mod_cgi/3752: CGI scripts arent killed when they are in deadlock
>Number: 3752
>Category: mod_cgi
>Synopsis: CGI scripts arent killed when they are in deadlock
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Fri Jan 22 14:30:01 PST 1999
>Last-Modified:
>Originator: viktor@nexus.hu
>Organization:
apache
>Release: 1.3.3
>Environment:
Redhat Linux, based on 4.2
gcc 2.7.2.1
>Description:
Earlier versions used to kill deadlocked CGI-scripts after some minutes.
After upgrading to this version, this behavior stoped.
I found an article describing that the TimeOut directive applies to this also,
but it is 300, and it doesn't work.
>How-To-Repeat:
>Fix:
>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! ]