I continued reading the CGI spec and a timeout is specifically mentioned in section 6.1 Response Handling: "The server MAY implement a timeout period within which data must be received from the script. If a server implementation defines such a timeout and receives no data from a script within the timeout period, the server MAY terminate the script process."
I think the process should be sent a signal and not left to run after a timeout. The process could either be stuck in an infinite loop or can be waiting on something that will never complete and the resources could be freed. I also believe the timeout should be reset whenever there is traffic. If this were the case, then I wouldn't have needed the -t option in the first place. The -t option would still continue to be useful for any processes with long response times and no traffic. For now the -t option I added is sufficient for me to get by with but I see there is room for slowcgi to be improved. -alfred
