3.0.0pre2: non-recursive remote listing breakage Looks like pre1's fix broke something else.
I noticed this when listing module/directory contents on servers known to be running versions 2.5.7 & 2.6.3. Not having (full) access to them, I replicated the errors using 2 machines on my home lan. # the machines lithium.elements.lan: the client. rsync 3.0.0pre2 for all tests. fluorine.elements.lan: the server with slack mirror mockup. All rsync versions from 2.6.9 back to 2.5.5 (to cover all the bases). # the test rsync rsync://fluorine.elements.lan/slackware/ # the results (2.6.9 to 2.6.4) motd & module contents displayed as expected. (2.6.3, as seen on lithium) <snip motd, if any> rsync: on remote machine: -d: unknown option rsync error: requested action not supported (code 4) at clientserver.c(473) rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(755) [receiver=3.0.0pre2] (2.6.2 to 2.5.5, as seen on lithium) <snip motd, if any> rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(596) [receiver=3.0.0pre2] (2.6.2 to 2.5.5, as seen in fluorine's logs) Oct 12 18:05:03 fluorine rsyncd[2733]: rsync on slackware/ from lithium.elements.lan (192.168.1.3) Oct 12 18:05:03 fluorine rsyncd[2733]: on remote machine: -d: unknown option Oct 12 18:05:03 fluorine rsyncd[2733]: rsync error: requested action not supported (code 4) at clientserver.c(424) Apologies for not reporting this earlier. Real life got in the way. Erik -- "Failure is not an option. (It comes bundled with Windows.)" "If at first you don't succeed, redefine success." -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
