Bug 3633 - rsync files-from using rsync daemon fails w/ error code 12
rsync files-from using rsync daemon fails w/ error code 12
Product: rsync
Classification: Unclassified
Component: core
Other Linux
: P3 normal
: ---
Assigned To: Wayne Davison
Rsync QA Contact
Depends on:
  Show dependency treegraph
Reported: 2006-03-28 02:01 UTC by reporta2000
Modified: 2006-10-15 13:26 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description reporta2000 2006-03-28 02:01:54 UTC
This fails:

rsync --verbose --progress --no-relative --files-from=/tmp/index rsync:// .

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 ;-)
Comment 1 Wayne Davison 2006-03-28 11:30:56 UTC
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.