On May 5, 2010, at 10:41 PM, Michael Renner wrote:
> I'm writing a compley backup application with rsync in shell.
>
> What I do to report errors: analyze the return code an internal table with
> error specifications and reporting these in clear text. The code:
You mean you just look at the r
Hello again,
Is there a reliable way I can parse the errors or get a direct list that rsync
produces while transferring? I'm writing a GUI and the only way to get errors
has been using regular expressions (all lines starting with "rsync:" for one)
but it's not always reliable because I don't kn
On May 1, 2010, at 4:29 AM, Matt McCutchen wrote:
> On Fri, 2010-04-30 at 14:21 +0700, Ryan Joseph wrote:
>> On Apr 30, 2010, at 12:54 PM, Matt McCutchen wrote:
>>> Rsync determines which of the files in the file list need a data
>>> transfer as it goes, so the o
On May 1, 2010, at 6:58 AM, Robert DuToit wrote:
> I don't know if this is what you are looking for but I have a GUI for rsync
> (Backuplist+) and now use unix "find directoryPath | wc -l" and it is very
> fast and gives you the total file count which reflects the rsync count in
> stats at the
On Apr 30, 2010, at 12:54 PM, Matt McCutchen wrote:
> On Fri, 2010-04-30 at 12:13 +0700, Ryan Joseph wrote:
>> I'm making a GUI for rsync and having some problems getting a reliable
>> indication of the files that will be transferred (so I can make a
>> progress bar f
I'm making a GUI for rsync and having some problems getting a reliable
indication of the files that will be transferred (so I can make a progress bar
from the results). I didn't see rysnc offered this so my plan has been to get a
list of files that will be transferred and count them as rsync rep
