Hi, On Thu, 2004-04-01 at 04:57, Sakesun Roykiattisak wrote:
Glad it work for you.
Recently I've found another issue with zopeservice.py. The zopeservice.InstanceService class use win32process.TerminateProcess() to terminate Zope process, which leave no room for Zope to perform normal exit process (I've found in the source-code that Zope have to do many things before exit). I'm worried if this could put ZODB at risk. I also wonder why they choose to spawn another pythonw.exe process to start Zope rather than run Zope in the zopeservice's python interpreter.
By the way, my 5 Zope instances is still working perfectly so far. And so do my Subversion services, which also terminate svn.exe process with TerminateProcess() ( I'm too lazy to do anything fancier :) )
Ok, this seems pretty windows typical. I'm using the apache batik library for my project here, and it requires a java vm running. (I use spawn for that). Whenever the Zope server goes down, the java process stays up and the lockfile for Zope remains under the control of this process. (Read: need to kill java before you can start zope again). I'm not sure if this is because of zope beeing terminated instead of shut down in a clean way. Christian -- Christian Theune, gocept gmbh & co. kg http://www.gocept.com - ct@gocept.com fon: 03496 3099112 fax: 03496 3099118 mobile: 0179 7808366