DO NOT REPLY [Bug 6175] New: write last transfer status when timeout or other error happens

samba-bugs at samba.org samba-bugs at samba.org
Sun Mar 8 11:07:57 GMT 2009


https://bugzilla.samba.org/show_bug.cgi?id=6175

           Summary: write last transfer status when timeout or other error
                    happens
           Product: rsync
           Version: 3.0.5
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: arekm at maven.pl
         QAContact: rsync-qa at samba.org


At this moment when timeout happens we get:

sending incremental file list
some.file
Timeout, server not responding.  0:33:43

rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
rsync: connection unexpectedly closed (99113 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.5]


I miss last info about tranfer before it failed. For example:

sending incremental file list
some.file
   222804096  40%   94.66kB/s    0:33:42
Timeout, server not responding.  0:33:43

rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
rsync: connection unexpectedly closed (99113 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.5]

Note the new "   222804096  40%   94.66kB/s    0:33:42" line.

Right now there is no information when (in terms of % transmitted) it failed
etc.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.


More information about the rsync mailing list