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
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+li...@gmail.comoptilude%2bli...@gmail.com
wrote:
Hi,
With Plone 4
On Fri, Sep 3, 2010 at 1:16 PM, Jim Pharis binbr...@gmail.com wrote:
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.
I thought the problem was only the .pid file, not the
I'm on 2.13.0a3 w/plone.recipe.zope2instanec-4.0.2. Under the scenario
Martin described, exiting a fg with ctrl-c, the lock file is cleaned up for
me. If I kill the service using Task Manager the lock file remains.
On Fri, Sep 3, 2010 at 12:33 PM, Sidnei da Silva
sidnei.da.si...@canonical.com
On 3 September 2010 17:06, Jim Pharis binbr...@gmail.com wrote:
I'm on 2.13.0a3 w/plone.recipe.zope2instanec-4.0.2. Under the scenario
Martin described, exiting a fg with ctrl-c, the lock file is cleaned up for
me. If I kill the service using Task Manager the lock file remains.
It seemed to be
