search for: 99113

Displaying 6 results from an estimated 6 matches for "99113".

Did you mean: 99,13
2009 Mar 08
5
DO NOT REPLY [Bug 6175] New: write last transfer status when timeout or other error happens
...arekm@maven.pl QAContact: rsync-qa@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: wr...
2010 Oct 27
0
DO NOT REPLY [Bug 2783] Random high loads during syncs (server side) / client stream errors
...code to handle long-running directory scans ./io.c:void maybe_send_keepalive(void) bug6175 write last transfer status when timeout or other error happens 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] bug7195 timeout reached while sending checksums for very large files -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this...
2010 Mar 02
2
DO NOT REPLY [Bug 7195] New: timeout reached while sending checksums for very large files
https://bugzilla.samba.org/show_bug.cgi?id=7195 Summary: timeout reached while sending checksums for very large files Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned at samba.org
2010 Oct 27
6
DO NOT REPLY [Bug 7757] New: with big file, rsync times out out when it should not; the sender is still responsive
...code to handle long-running directory scans ./io.c:void maybe_send_keepalive(void) bug6175 write last transfer status when timeout or other error happens 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] bug7195 timeout reached while sending checksums for very large files -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this...
2008 Aug 16
5
DO NOT REPLY [Bug 5695] New: rsync local timeout
https://bugzilla.samba.org/show_bug.cgi?id=5695 Summary: rsync local timeout Product: rsync Version: 3.0.3 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: gabriele.tozzi@gmail.com QAContact:
2008 May 21
35
DO NOT REPLY [Bug 5478] New: rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32)
https://bugzilla.samba.org/show_bug.cgi?id=5478 Summary: rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32) Product: rsync Version: 3.0.3 Platform: Other URL: https://bugzilla.samba.org/show_bug.cgi?id=1959 OS/Version: Linux Status: NEW Severity: normal