Re: --no-dirs seem not to explude "d"

2008-03-24 Thread Anthony Morton
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

Re: --no-dirs seem not to explude "d"

2008-03-24 Thread Wayne Davison
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).

Rsync 3.0.1pre1 released

2008-03-24 Thread Wayne Davison
I have just released rsync 3.0.1pre1 for release testing. This is a bug-fix release, which includes fixes/improvements for several issues in the daemon-exclude code. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a full

Re: Issue with rsync 3.0.0 and iconv

2008-03-24 Thread Sergi Baila
Thanks for your answer Wayne, I've run the command with -vvv and got a 13 megs output. ;-) The file bzipped is just under 1M, I can send to you directly by email if you want. There seems to be certain unsync between the moment this line appears: received request to transfer non-regular file: 86

--no-dirs seem not to explude "d"

2008-03-24 Thread Simo Sorce
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