search for: msgs2stderr

https://bugzilla.samba.org/show_bug.cgi?id=5407 Summary: hlink.c:480: finish_hard_link: Assertion `flist != ((void *)0)' failed. Product: rsync Version: 3.0.2 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=11166 Bug ID: 11166 Summary: running with -vvv causes a hang Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: pskocik at

https://bugzilla.samba.org/show_bug.cgi?id=11949 Bug ID: 11949 Summary: A malicious sender can still use symlinks to overwrite files Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee:

...AssignedTo: wayned at samba.org ReportedBy: orion at cora.nwra.com QAContact: rsync-qa at samba.org I am finding that rsync is failing to sync up certain combinations (sender and receiver) of sparse files when using compression. With 3.1.1pre1 I just see: # rsync -axHS -z --msgs2stderr /export/images/Fedora-Minimal-armhfp-20-1-sda.raw barry:/export/tmp/ rsync: [sender] write error: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(820) [sender=3.1.1pre1] With some older versions I can see the server fail with "inflate returned -3 (0 bytes)&...

https://bugzilla.samba.org/show_bug.cgi?id=10372 Summary: rsync 3.10 error in protocol data stream while rsync 3.0.9 runs through Product: rsync Version: 3.1.0 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

...generator. The following releases show the problem: master, 3.1.3, 3.1.2, 3.1.0 Release 3.0.9 and older do not exhibit the problem. Each of the following workarounds were successful for my customer and in my testing: - use an older version of rsync (3.0.9 or older) - specify rsync option --msgs2stderr - perform the rsync under a userid with the same group as the source files Thanks for your consideration, and please let me know if there's anything else I can provide to help. Regards, -- Mark Vitale mvitale at sinenomine.net -- You are receiving this mail because: You are the QA Contact f...

https://bugzilla.samba.org/show_bug.cgi?id=5795 Summary: error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4] Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: blocker Priority: P3 Component: core AssignedTo:

I am involved with the development of lbackup. This message to the rsync mailing list is related to the following thread on the lbackup-disccussion mailing list : http://tinyurl.com/lbackup-discussion-diskfull Essentially, I am curious to if any one using rsync 3.0.7 on Mac OS (10.6) Server has experienced an out of disk space error and not had a message similar to the following reported : >

https://bugzilla.samba.org/show_bug.cgi?id=10527 Summary: Rsync Deadlock when copying files Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: dah4k0r at gmail.com

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