One more thing, what does the disk where the Data.fs resides look like?
On Mon, 28 Aug 2006, Dennis Allison wrote:
>
> Kris,
>
> I assume you have a backup of the Data.fs. If you do, nothing is really
> lost.
>
> Have you compressed the Data.fs? There is an option
Kris,
I assume you have a backup of the Data.fs. If you do, nothing is really
lost.
Have you compressed the Data.fs? There is an option in the control panel
to do this. I can be run on a live machine, but you may not want to do so
given the size of stuff. I'd do it on a quiet machine. This
On Fri, 24 Mar 2006, Jim Fulton wrote:
> Andreas Jung wrote:
>
> > I propose to deprecate XML export/import for Zope 2.10 and to remove it
> > in Zope 2.12. We don't loose any functionality since .zexp is working
> > fine. I don't know of any active projects/code that really uses XML
> > expor
I've been seeing the same sort of messages and many others. I've assumed
that they are due to the fact that nearly every Product will need some
polishing as we approach the 2.10 and 2.11 releases. Some of the
diagnostics refer to subsystems in Zope itself which still use old rather
than new
the README I neglected to read as this is the fifth
version of ZSyncer I've installed and I thought I knew the product.
On Wed, 1 Feb 2006, Dennis Allison wrote:
> Paul,
>
> Just moved all our systems to ZSyncer 0.7.0 and have encountered a
> problem related to authentication.
Paul,
Just moved all our systems to ZSyncer 0.7.0 and have encountered a
problem related to authentication.
In our past setup, using ZSyncer 0.5.1, we use the ability to specify
a user:password to provide a single authorization mechanism that could be
used by all of our developers.
Now we've s
+1 on the lot if you are looking for votes.
On Tue, 20 Dec 2005, Andreas Jung wrote:
> Hi,
>
> for next release we plan to replace several parts with the corresponding
> components from Zope 3 (e.g. ZPT´). Philipp is working on a proposal on
> that issue. In addition I would like to get ri
sion variable initialization in a Script(Python) object has a
downside because one cannot set a _p_changed attribute and so must rely on
the assignment paradigm. Perhaps the interface should be in a Product or
External Method which is less constrained.
Anyhow, David, thanks for the assist.
On Mon, 19 D
Chris McDonough identified a persistence problem with the routine(s) that
manage sessions variables. (Thanks Chris) I have put the correction in
place which resolved some (but not all) of the problems.
There are still problems which are apparently due conflicts in accessing
the session variab
On Thu, 15 Dec 2005, Chris McDonough wrote:
> Trimmed zodb-dev off the cc list.
>
> On Dec 15, 2005, at 2:24 PM, Dennis Allison wrote:
>
> > The systems are running a Zope/ZEO combination with a store
> > configuration
> > of:
> >
> > #
> &
Zope 2.8.4, ZODB 3.4.2
Chris,
I'm pretty sure that I mentioned having done that in one of my postings.
I have followed your recommendations, but the problem remains. (um...
persists )
The systems are running a Zope/ZEO combination with a store configuration
of:
#
# Temporary storage d
We probably want an "ALL" level as well which would map to the "NOTSET"
of the Python logging code and log everything.
Florent, I don't see a TRACE level in this list. Did you think one was
needed?
On Mon, 5 Dec 2005, Florent Guillaume wrote:
> Chris Withers wrote:
> >> # In the days of z
Dieter's point about not includeing the traceback makes sense
if all it does is report on the reporting code.
Wlorent, do you envision a single ConflicError or two -- one which
succeeds on retry and another where the retry fails?
On Sun, 4 Dec 2005, Dieter Maurer wrote:
> Florent Guillaume wro
1. INFO
2. Yes, with traceback (necessary as these are heissenevents)
3. ERROR
4. don't care -- we can adapt
Thanks Florent for taking the lead on this. I think it's a great
help.
On Fri, 2 Dec 2005, Florent Guillaume wrote:
> Please vote for the level at which you want to log retried con
Thanks, I'll take a look.
On Wed, 23 Nov 2005, Michael Dunstan wrote:
> On 11/22/05, Florent Guillaume <[EMAIL PROTECTED]> wrote:
> > Dennis Allison wrote:
> > > *** you are correct -- this is the easy hack on the event.log. It's much
> > > hard
On Mon, 21 Nov 2005, Chris McDonough wrote:
> On Nov 21, 2005, at 2:10 PM, Dennis Allison wrote:
> >
> > Conflicts and how they interact with the database and sessioning
> > machinery
> > is my hot button right at the moment )-: I Hope I have not
> > include
session[XXX] = sss"
> (at least, if there is a high chance that "session" already
> contains the correct value).
Session variable present a particularly vexing problem since they may
trigger writes even though they are apparently read-only.
Chris McDonough <[EMAIL
That's what I have been doing. -d
On Wed, 30 Mar 2005, Florent Guillaume wrote:
> I'd like to disable FTP by default, by commenting it out in
> skel/etc/zope.conf. The reason is that it's better to open as few ports
> as possible by default.
>
> Opinions ?
Athlon
machines, 4GB memories, and hardware raid controllers in a RAID-10
configuration. It's possible that our problems with RH9 may be tied
to some problem with their Athlon SMP systems.
Thanks for your comments and advise.
On Thu, 8 Jan 2004, Tres Seaver wrote:
> Dennis Allison wrote:
3 for everything else except RedHat tools).
On Thu, 8 Jan 2004, Tres Seaver wrote:
> Dennis Allison wrote:
>
> > Does this mean that Zope 2.6.3 is compatible with Python 2.3.3? I would
> > be nice to retire 2.1.3.
>
> A significant part of the effort for 2.6.3 (whi
Brian --
Does this mean that Zope 2.6.3 is compatible with Python 2.3.3? I would
be nice to retire 2.1.3.
-dra
On Thu, 8 Jan 2004, Brian Lloyd wrote:
> Zope 2.6.3 Release and Security Update
>
> Zope 2.6.3 contains a number of security related fixes for issues
> resolved during
Matt--
I've run both RH7.2 and RH7.3 and IMHO RH7.3 is more stable, etc etc.
-dra
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lis
22 matches
Mail list logo
