On Sep 16, 2006, at 5:02 AM, Christian Theune wrote:
...
*If* someone else had that problem too, I'd propose to change away
from
the fallback of using zope.conf.in (we force people to create the
principals too, don't we?)
This problem hasn't happened very often. I would find having to copy
Jim Fulton wrote:
On Sep 16, 2006, at 5:02 AM, Christian Theune wrote:
...
*If* someone else had that problem too, I'd propose to change away from
the fallback of using zope.conf.in (we force people to create the
principals too, don't we?)
This problem hasn't happened very often. I
Christian Theune wrote:
Gah.
Mea culpa.
Until recently I didn't know that the zope.conf.in could even be copied
over to zope.conf, because every checkout that I ever used always picked
up the zope.conf and nothing ever told me to copy it. (Although I was
slightly annoyed having to edit
On Saturday 16 September 2006 05:10, Philipp von Weitershausen wrote:
*If* someone else had that problem too, I'd propose to change away from
the fallback of using zope.conf.in (we force people to create the
principals too, don't we?)
Right. I wouldn't mind that. +0 from me.
It is all
Stephan Richter wrote:
On Saturday 16 September 2006 05:10, Philipp von Weitershausen wrote:
*If* someone else had that problem too, I'd propose to change away from
the fallback of using zope.conf.in (we force people to create the
principals too, don't we?)
Right. I wouldn't mind that. +0 from
Philipp von Weitershausen wrote:
Stephan Richter wrote:
On Saturday 16 September 2006 05:10, Philipp von Weitershausen wrote:
*If* someone else had that problem too, I'd propose to change away from
the fallback of using zope.conf.in (we force people to create the
principals too, don't we?)
Stephan Richter wrote:
Hi everyone,
I just noticed that zope.conf.in has now the following entry:
zodb
demostorage
zeoclient
server localhost:8100
storage 1
cache-size 20MB
/zeoclient
/demostorage
/zodb
This means that ZEO has to start up to run Zope after a default check
