2009/3/23 gert <[email protected]>: > > On Mar 22, 9:41 pm, Graham Dumpleton <[email protected]> > wrote: >> 2009/3/22 gert <[email protected]>: >> >> > Can you kill something that still has to return some really big >> > response ? >> >> This point was already explained if you had paid attention to the >> descriptions given previously of how things worked. What was said was: >> >> >> Does it stop the process immediately, leaving code after the >> >> os.kill() call unexecuted? >> >> > No, it performs an orderly shutdown of the daemon process, attempting >> > to wait for all current requests to finish before actually killing the >> > process. As a fail safe however, if the active requests take more than >> > the shutdown timeout, default of five seconds, then it will forcibly >> > kill off the process. >> >> Also have a look at the online documentation for 'shutdown-timeout' >> option for WSGIDaemonProcess directive in: >> >> http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIDae... >> > > Does maximum-requests=1 have the same result as the script ?
I already said that what was being done in the script presented was the wrong way of going about various things, so please do not use the script as any indication of what would be regarded as good practice. I would suggest you explain properly what you are trying to achieve and then we can work out the proper way of doing it and whether it is a sensible thing to do or not. Things are too muddied now as to what anyone wants or expects. I am not going to try and answer until you properly explain what you want. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
