samba-bugs@samba.org
2006-Mar-28 08:02 UTC
DO NOT REPLY [Bug 3633] New: rsync files-from using rsync daemon fails w/ error code 12
https://bugzilla.samba.org/show_bug.cgi?id=3633 Summary: rsync files-from using rsync daemon fails w/ error code 12 Product: rsync Version: 2.6.0 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: reporta2000@yahoo.com QAContact: rsync-qa@samba.org This fails: rsync --verbose --progress --no-relative --files-from=/tmp/index rsync://192.168.0.1/aservice . Same using --files-from=:/tmp... Same using remote::aservice Using rsync://remote::aservice fails with connection refused (doesn't really connect according to tcpdump) Remote log: syntax or usage error (code 1) at options.c(679) Local error: connection unexpectedly closed (166 bytes read so far) error in rsync protocol data stream (code 12) at io.c(189) Remote and local are rsync 2.6.0. Using ssh as remote shell, the above works. But who would want to use encryption for that ;-) -- 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.
samba-bugs@samba.org
2006-Mar-28 17:31 UTC
DO NOT REPLY [Bug 3633] rsync files-from using rsync daemon fails w/ error code 12
https://bugzilla.samba.org/show_bug.cgi?id=3633 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #1 from wayned@samba.org 2006-03-28 11:30 MST ------- An initial fix for --files-from sent to a daemon was made in 2.6.1, but it was fixed the rest of the way for 2.6.3, so upgrading is your best bet. You'll also need at least 2.6.4 for --no-relative to be properly forwarded to a remote sender, so be sure to upgrade to something modern, like 2.6.7. -- 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.
Seemingly Similar Threads
- DO NOT REPLY [Bug 3768] New: --no-specials in Rsync 2.6.8 breaks compatibility with 2.6.0-r6 Mirroring system
- DO NOT REPLY [Bug 3554] New: Second copy of same rsync daemon should notice pid file and quit
- DO NOT REPLY [Bug 3594] New: --delete doesn't delete destination files that don't exist at the source
- DO NOT REPLY [Bug 5633] New: --pidfile option for rsync daemon
- DO NOT REPLY [Bug 4079] New: rsync fails with --inplace, --link-dest and --no-whole-file