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