Running zopectl debug runs your normal instance with additional debug
breakpoints and pdb started. So in the same way that you cannot start
the same instance twice, you cannot start your instance and a zopectl
debug at the same time.
Florent
Jeff Kowalczyk [EMAIL PROTECTED] wrote:
Chris
On 5 Jul 2005, at 12:20, Florent Guillaume wrote:
Running zopectl debug runs your normal instance with additional debug
breakpoints and pdb started. So in the same way that you cannot start
the same instance twice, you cannot start your instance and a zopectl
debug at the same time.
Umh,
On 5 Jul 2005, at 12:55, Jens Vagelpohl wrote:
Umh, that's incorrect. zopectl debug has nothing to do with debug
breakpoints or pdb. And you can run it right alongside your running
Zope instance. All it does is present you with a Python prompt
where the root object is bound to app, nothing
On Mon, 04 Jul 2005 22:18:34 +, Jeff Kowalczyk wrote:
This is a local ReiserFS partition. The zope and zeo are on the local
machine, communicating over port .
I just checked, and it is not the 'zopectl debug' that fails, it is the
second connection to the running zeo; if you run
Chris McDonough wrote:
If you dont think it's file permissions, one thing this could also be...
is your data.fs on an NFS partition? flock doesn't work well on NFS.
This is a local ReiserFS partition. The zope and zeo are on the local
machine, communicating over port .
I just checked, and
