The following reply was made to PR mod_cgi/3751; it has been noted by GNATS.
From: Dean Gaudet [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Subject: Re: mod_cgi/3751: CGI scripts arent killed when they are in
deadlock (fwd)
Date: Thu, 22 Apr 1999 02:41:41 -0700 (PDT)
-- Forwarded message --
Date: Thu, 22 Apr 1999 10:22:11 +0200
From: Viktor Bodrogi [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: mod_cgi/3751: CGI scripts arent killed when they are in deadlock
Hi!
Thanks for answering my question, but it's already eliminated
by using fcgi. So I even don't remember the situation,
but I'm sure it was a problem for me, having some deadlocked cgi's
runing for hours until I kill them. Probably they did write anything,
but in this case they should killed when the client disconnects,
shouldn't they?
Anyway, mod_fcgi is a great solution, we have a very overloaded server,
with normal cgi the processor load was about 50 sometimes,
now it's always under 5. According to my benchmarks the server
answers about 20-30 times faster now (without load).
Thanks anyway!
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
[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: CGI scripts arent killed when they are in deadlock
State-Changed-From-To: open-feedback
State-Changed-By: dgaudet
State-Changed-When: Tue Apr 20 20:53:47 PDT 1999
State-Changed-Why:
I'm not sure what you mean by deadlocked ... ?
If a timeout occurs the connection to the CGI is closed.
The timeout won't happen if the CGI writes anything, unless
the client never reads it.
Do you have a small example we can reproduce the problem with?
If I test CGIs that just sleep forever the timeout works
fine.
Dean
