DO NOT REPLY [Bug 6020] New: support/rrsync fails when server-side options include "-e."

samba-bugs at samba-bugs at
Wed Jan 7 22:25:25 GMT 2009

           Summary: support/rrsync fails when server-side options include "-
           Product: rsync
           Version: 3.0.4
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned at
        ReportedBy: gwilliam at
         QAContact: rsync-qa at

When using support/rrsync (rsync-3.0.4), if server-side options look like
  "--server -e.<whatever>"
the script fails, leading to a client-side message like this:

rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(632) [sender=3.0.4]

This does not appear to happen when the 'e' follows other characters on the
server side. For example, "rsync -a file rem:." on the client side results in
arguments that look like this on the server: "--server -logDtpre.iLs . .".
In this case, everything is fine.  On the other hand, if you try
"rsync file rem:." on the client side, the arguments on the server look
like this: "--server -e.Ls . .", and it fails.

I believe the problem is on line 147 of support/rrsync.  If I change it from
      next if /^-$short_no_arg+(e\d*\.\w*)?$/o || /^-$short_with_num\d+$/o;
      next if /^-$short_no_arg*(e\d*\.\w*)?$/o || /^-$short_with_num\d+$/o;

the problem appears to go away.


Configure bugmail:
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the rsync mailing list