[Top][All Lists]

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

Re: [Duplicity-talk] Re: dbus patch

From: Kenneth Loafman
Subject: Re: [Duplicity-talk] Re: dbus patch
Date: Tue, 04 Nov 2008 13:03:24 -0600
User-agent: Thunderbird (X11/20080925)

My take on any backup system is that unless it is usable from cron and a
command line, its absolutely useless.  GUI's are nice for setup and
monitoring, but if either the GUI or human intervention is required for
execution, then you've broken the backup process because now you're
relying on the most undependable part of the system, the human, in order
to get it started and to run on a set schedule.

Whatever solution we come up with will have to support running via cron
as the primary mode and managed as the secondary mode.  Dbus may be an
aid in monitoring and possibly managing the process, but it must be
optional so standalone backups are not compromised.


Edgar Soldin wrote:
> well,
> currently duplicity is small and only depending on packages that are
> necessary for the job to be done. Dbus is not one of them.
> 3MB is lots in a embbedded device environment, eg. just checked my WRT54
> router w/ linux on it.. it has 2MB where at least 1MB is already filled
> .. but currently it could theoretically drive duplicity as librsync,
> python, gnupg packages are available - this won't be the case with dbus
> as dependency
> I don't see why to make a desktop component mandatory for a application
> that might be used only from shell interfaces by some.
> I'd suggest to go back one step and reconsider other established ways
> of  interprocess communication. Wouldn't sockets, signals, named pipes
> (you name them) do the trick as well? One can still write a dbus
> translator for these interfaces, if necessary. Plus these interface
> could be used by commandline based wrappers, like bash ftplicity ;)
> just my 2cents.. ede

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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