We're experimenting with Zope 2.1 and FastCGI; this marks the first time I've seriously used ZServer, and I have a possibly silly question. An odd behaviour I've noticed is that 'Shutdown' on the Control Panel isn't shutting down Zope; while the usual SystemExit traceback is printed, the Zope process hangs around, preventing FastCGI from starting a new Zope server on the next request.

Before I spend some time tracking this down, I want to be sure that this isn't expected behaviour; should ZServer be shut down differently, by some means other than the control panel?

Yes 'shutdown' from the Control Panel is supposed to cause Zope to exit. Let's see, after you shutdown will Zope accept any more web connection? Does 'restart' from the Control Panel work? Does shutdown via HTTP (as opposed to FastCGI) work? What web server, fastcgi module, and platform are you using? It sounds to me like a problem with the FastCGI server, though if you can't shutdown Zope with plain HTTP then there is a deeper problem. Let me know and I'll look into it. Also just to clarify FastCGI operation -- normally once you shutdown Zope your web server won't be able to restart Zope, even though this is how many FastCGI applications work. You should use Zope's 'restart' capability if you just want to restart it. Good luck! -Amos -- Amos Latteier mailto:amos@digicool.com Digital Creations http://www.digicool.com