On Mon, 2008-03-24 at 23:10 -0700, Wayne Davison wrote:
> On Mon, Mar 24, 2008 at 09:11:43AM -0400, Simo Sorce wrote:
> > The notes say to use --no-d, but using it seem not to help, and in
> > fact the remote host is still sent the 'd' option:
>
> Yeah, the code was erroneously overriding the --n
The -d option was added in 2.6.4, almost exactly 3 years ago. There
seems to be a significant amount of 2.6.3 still around (which is 3.5
years old), which is a little sad to see, but I suppose not that
unexpected.
Rsync 2.6.3 is the default on OS X 10.5 Leopard, released in October
last
On Mon, Mar 24, 2008 at 09:11:43AM -0400, Simo Sorce wrote:
> The notes say to use --no-d, but using it seem not to help, and in
> fact the remote host is still sent the 'd' option:
Yeah, the code was erroneously overriding the --no-d option, so I fixed
that in the latest version (see 3.0.1pre1).
Running rsync against an old server I get:
rsync rsync://host/dir
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync: error: error in rsync protocol data stream (code 12) at io.c(600)
[receiver=3.0.0]
This seem to be a problem described in the second paragraph of t
