Florian, > I do hope that most people moved to fastcgi by now and maybe it's time > to shake out scripts that don't handle termination correctly?
I don't think there is a "move to fastcgi" happening. Fastcgi is a complicated protocol compared to cgi. Various projects can be implemented with a simple and straightforward cgi script. I don't see a reason to start shaking out simplicity. > So ok, fine, go ahead, terminate & kill after timeout. If we are going to kill processes then I would recommend not killing a process while the client is still connected. I would start the kill timeout after the client disconnects. This will solve a good set of concerns: - My issue: client receiving large amounts of data from a long running cgi - Omar: "client is purposefully reading data slowly / kill the scripts at specific points" - Claudio: "'dead' CGI scripts piling up because they hung on something." I think it's standard Steven's networking practice to keep processing as long as the client is willing to wait, with respect to timeouts. -alfred
