rsync: connection unexpectedly closed (0 bytes received so far)

[Bruce Korb]

Hi Matt,

On Tue, Mar 23, 2010 at 4:23 PM, Matt McCutchen <matt at mattmccutchen.net> wrote:
> "Yes" is the default, so you have to explicitly write "use chroot = no".

Done.  No effect.

> --rsync-path='strace -f -o ~/rsync.strace rsync' to the client.

I now have an strace output file.  It opens rsyncd.conf correctly
and reads in all the data in one gulp.  I've trimmed the strace to start from
there.  Notice that it tries to open the log file and fails because it
isn't found.  The fun part is the fact that the file is there.  So, I suspect
it is running in some sort of chrooted jail, despite the fact that
"use chroot" is set to "no"?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rsync.strace
Type: application/octet-stream
Size: 14036 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/rsync/attachments/20100323/671173bd/attachment.obj>