[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Re: dbus patch

From: Richard Scott
Subject: Re: [Duplicity-talk] Re: dbus patch
Date: Thu, 6 Nov 2008 12:14:39 -0000 (UTC)
User-agent: SquirrelMail/1.5.1


If I'm understanding things correctly, we'll know if we stop duplicity part way 
through via GUI as
the GUI will have sent duplicity a kill signal.

We should also know if duplicity dies while running as its error code won't be 

> If the user cancels, they have left overs.  And Déjà Dup (in bzr)
> automatically calls "cleanup" if the user cancels, but we'd still end up with 
> cruft if for some
> reason Déjà Dup got killed or some error occurred halfway through.

If duplicity leaves things in a messy state due to a failed backup couldn't we 
we just run a
cleanup before each backup?

This is what I currently do via cron and it seems to work well for me :-)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]