Re: [Zope-dev] .lock files on Windows
On 3 September 2010 17:06, Jim Pharis 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 happening intermittently. But it happened on two different PCs running Windows XP. Instances were started with "bin\instance fg" and killed with Ctrl+C. 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 )
Re: [Zope-dev] .lock files on Windows
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> wrote: > On Fri, Sep 3, 2010 at 1:16 PM, Jim Pharis 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 .lock. Can you > confirm? The .lock file should go away if the process dies in any way, > but the .pid file seems to only be deleted on clean shutdown. > > -- Sidnei > ___ 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 )
Re: [Zope-dev] .lock files on Windows
On Fri, Sep 3, 2010 at 1:16 PM, Jim Pharis 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 .lock. Can you confirm? The .lock file should go away if the process dies in any way, but the .pid file seems to only be deleted on clean shutdown. -- Sidnei ___ 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 )
Re: [Zope-dev] .lock files on Windows
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 > 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 ) > ___ 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 )
