> (Package was locally compiled. The only difference between custom > version and Debian version is that the custom version was compiled with > --disable-fork, so that I could run it under a process supervisor.)
You can achive the same thing without recompiling, just pass a "-o nodaemon" option to Thy. > When a CGI script fails to run (e.g. syntax error in a Perl script), thy > will either > - just close the connection to the browser > - go into an (infinite?) loop, eating the CPI > or > - spit out some garbage to the browser > > Behaviour seems to be unpredictable. > > Ideally, I think that thy should give a status code of 500 (Internal > Server Error) if the CGI script dies. I think at least that is what > Apache does. Indeed, it should. What happens is a nasty race: the CGI goes down and gets cleaned up before Thy fills in the CGI's PID associated with the appropriate session in its tables. Thus, the session remains in a stale state. That will either result in getting into an infinite loop, or timing out, and closing the connection. I couldn't reproduce the garbage splitting, though... Anyways, a fix is in the works, and will be in the next upstream release. (A workaround is ready already, but I want to fix this properly). Cheers, -- Gergely Nagy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
