[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Continuing an interrupted backup.
|
From: |
Gabriel Ambuehl |
|
Subject: |
Re: [Duplicity-talk] Continuing an interrupted backup. |
|
Date: |
Fri, 23 Nov 2007 21:39:06 +0100 |
|
User-agent: |
KMail/1.9.6 (enterprise 0.20070907.709405) |
On Thursday 01 November 2007 15:14:23 Kenneth Loafman wrote:
> Simpler would be a file like '/path/duplicity-halted' which could be
> removed in order to restart. You could also put the error reason in
> the file itself. Or, if you do use a socket, you could actually post
> progress messages to the socket... just a thought.
One thing just struck me: considering that duplicity is Python and Python
comes with the wonders of pickle, wouldn't it be possible to simply dump all
state using pickle (for example, if some signal other than SIGTERM or SIGKILL
is received) and reload it upon restart?
signature.asc
Description: This is a digitally signed message part.