[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:20:31 -0000 (UTC) |
User-agent: |
SquirrelMail/1.5.1 |
Hi,
>> do). That is, with several of the IPC schemes, it's difficult to monitor a
>> duplicity instance
>> you didn't start.
>
> Yeah, discoverability is always a problem...
If you've started duplicity from the command line then you'd not need a GUI to
monitor it, no?
also, if it started from cron and you piped output from duplicity into a helper
applicaiton you
would be able to monitor it as your helper application would know how to talk
back to your GUI.
You could think of the helper applicaiton as a translator for XML -> dbus??
A suggestion could be that a default xml output is displayed as soon as
duplicity startsdisplaying
information about the process i.e pid, command options etc. This way the helper
would know more
about what its watching and be able to display such information in the GUI.
Rich.
- Re: [Duplicity-talk] Re: dbus patch, (continued)
- Re: [Duplicity-talk] Re: dbus patch, Dan Muresan, 2008/11/04
- Re: [Duplicity-talk] Re: dbus patch, Michael Terry, 2008/11/04
- Re: [Duplicity-talk] Re: dbus patch, Dan Muresan, 2008/11/04
- Re: [Duplicity-talk] Re: dbus patch, Edgar Soldin, 2008/11/04
- [Duplicity-talk] asynchronous-uploads, Richard Scott, 2008/11/04
- Re: [Duplicity-talk] asynchronous-uploads, Peter Schuller, 2008/11/07
- Re: [Duplicity-talk] Re: dbus patch, Michael Terry, 2008/11/05
- Re: [Duplicity-talk] Re: dbus patch, Dan Muresan, 2008/11/06
- Re: [Duplicity-talk] Re: dbus patch, Michael Terry, 2008/11/06
- Re: [Duplicity-talk] Re: dbus patch, Dan Muresan, 2008/11/06
- Re: [Duplicity-talk] Re: dbus patch,
Richard Scott <=
- Re: [Duplicity-talk] Re: dbus patch, Edgar Soldin, 2008/11/04
- Re: [Duplicity-talk] Re: dbus patch, Kenneth Loafman, 2008/11/04