https://bugs.launchpad.net/collective.buildout/+bug/596839 Killing a fg instance with ctrl-c isn't the only scenario where the lock and pid files don't get cleaned up. On Fri, Sep 3, 2010 at 11:46 AM, Martin Aspeli <optilude+lists@gmail.com<optilude%2Blists@gmail.com>
wrote:
Hi,
With Plone 4 and thus Zope 2.12.10, we've noticed a problem that I think only affects Windows. Can anyone confirm or shed some more light?
Basically, if we run an instance (installed via plone.recipe.zope2instance as bin\instance) in the foreground (bin\instance fg) and then kill it with Ctrl+C, the var\instance.lock and var\instance.pid files are not cleaned up. These need to be manually deleted, otherwise Zope refuses to start up with the confusing message "Please stop the instance before starting it".
Martin _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )