test instance problems
Seairth Jacobs <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <[email protected]> |
I am using mod_fastcgi with the following setup: Windows XP Apache 2.0.58 mod_fastcgi 2.4.2 The CGI script is written in Python (using the flup package). In order to get the two talking to each other I am using the following directives: FastCgiConfig -autoUpdate -maxClassProcesses 1 -maxProcesses 1 -minProcesses 1 -processSlack 1 FastCgiServer cgi-bin/fcgi_handler.py -port 8081 Since I am using this for active development, I want the python app to reload when I update it. Unfortunately, "-autoUpdate" does not seem to work. As an alternative, I set up my code to handle a single request and then exit. As expected, the old app instance terminates a new instance of the app is automatically created, effectively making this act like traditional CGI. But this also does not seem to work perfectly. I encountered the "[...] has failed to remain running for 30 seconds given 3 attempts, its restart interval has been backed off to 600 seconds" message in the error log (and the associated delay). So, is there a way to stop that behavior? If not, is there a way to get the -autoUpdate directive working properly with the above setup? Seairth Jacobs ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/