https://bugzilla.samba.org/show_bug.cgi?id=10532
--- Comment #4 from Wayne Davison <way...@samba.org> 2014-04-29 17:13:13 UTC --- Rsync 2.3.2 refuses to interact with protocol 31. If you wish to tweak 2.3.2 to not be so draconian, please be my guest, but you'd be better off upgrading the hugely ancient rsync instead. There's nothing that a modern rsync can do about the refusal of an old rsync to interact with it since it must advertise its maximum protocol (and it doesn't know how old the server is beforehand). More modern rsyncs are more forgiving about allowing later versions, but only up to protocol 40 at present. It would be nice to remove the max-protocol check altogether, but the check was added to try to figure out when it received some ascii garbage instead of a valid protocol value, so we need a better "I got garbage" check (which should really have been implemented in a better manner from the start). So, if you run into an old rsync and you can't upgrade it, just remember to use --version=30 to work around its deficiency. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
