On 27/10/2007 Andreas Jung wrote:
This is not the point. rsync will run into if the file to be synced changes
in-between the sync operation. This will happen with the Data.fs - it won't
happen with a static copy. An inconsistent copy of the Data.fs is not the
problem since invalid transaction
On 27/10/2007 Tino Wildenhain wrote:
Nobody is wrong. Your #debian guys just had not all informations.
Zope is always appending to Data.fs, copy (cp) works linear, so
it would always maintain a consistent state of this file.
(It either copies before or after the last append operation)
rsync
On Sun, 28 Oct 2007 20:15:27 +0100, Jonas Meurer wrote:
i'll change that to backup a local copy of the Data.fs instead in
future. a simple solution would be to run 'cp Data.fs Data.fs.safe' for
every instance just before backuppc starts the rsync process.
We use the repozo backup (and
Log message for revision 81167:
Backported discouraged warning for manage_* events from trunk
Changed:
U Zope/branches/2.10/doc/CHANGES.txt
U Zope/branches/2.10/lib/python/OFS/CopySupport.py
U Zope/branches/2.10/lib/python/OFS/subscribers.py
-=-
Modified:
Summary of messages to the zope-tests list.
Period Sat Oct 27 13:00:00 2007 UTC to Sun Oct 28 13:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Sat Oct 27
On Oct 27, 2007, at 3:39 PM, TIm TerlegÄrd wrote:
When using zc.buildout I discovered that it installed a part that I
didn't
specify in the 'parts' option. This happened because I referenced this
part somewhere else. Is this how it's supposed to be?
Yes.
Jim
--
Jim Fulton
Zope