Is there a configuration directive or some trick that I could use to kill a CGI script if it runs for longer than, say, 120 seconds?If any of my scripts run for longer than 30 seconds or so, they are certainly in a loop, and will continue forever, until I notice and kill them manually.
I've not
-Original Message-
From: Steve Swift [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 20, 2006 9:05 AM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] CGI Timeouts?
Is there a configuration directive or some trick that I could
use to kill a CGI script if it runs
But apache won't (can't!) kill the process that's looping...The operating system is Linux. The separate threads are spawned as apache (in our case) but there is still the root process running httpd - that should have no problems killing of looping CGI processes, if it wanted to.
However, I'll
It was thus said that the Great Steve Swift once stated:
But apache won't (can't!) kill the process that's looping...
The operating system is Linux. The separate threads are spawned as apache
(in our case) but there is still the root process running httpd - that
should have no problems
Hi,
I didn't follow the full email thread so I apologise if this is off-topic.
Apache 1.3.x definetly has support for looping CGI apps - see
src/main/alloc.c:alloc.c:free_proc_chain().
When a new CGI app is spawned, it is registered in this 'proc chain'
list and when timeout occurs at cgi
