various "rsync: connection unexpectedly closed" errors on debian

[wearitdown at myrealbox.com]

Hi jw schultz,

>Please check your rsync log file (created by the daemon) for
>error messages.  Also try without compression.
>  
>

When I sync'ed against other servers, my rsync client process always ran 
without --compress.  Nevertheless, I've tried increasing verbosity by 3, 
and this is what I get:

    receiving file list ...
    recv_file_name(.)
    recv_file_name(net-zope)
    recv_file_name(net-zope/btreefolder2)
    [snip]
    recv_generator(x11-wm/xpde/xpde-0.2.0.ebuild,49890)
    x11-wm/xpde/xpde-0.2.0.ebuild is uptodate
    recv_generator(x11-wm/xpde/xpde-0.3.0.ebuild,49891)
    x11-wm/xpde/xpde-0.3.0.ebuild is uptodate
    generate_files phase=1
    recv_files(metadata/timestamp)
    recv mapped metadata/timestamp of size 29
    metadata/timestamp
    rsync: connection unexpectedly closed (1494175 bytes read so far)
    rsync error: error in rsync protocol data stream (code 12) at io.c(165)
    _exit_cleanup(code=12, file=io.c, line=165): about to call exit(12)
    rsync: connection unexpectedly closed (1494155 bytes read so far)
    rsync error: error in rsync protocol data stream (code 12) at io.c(165)
    _exit_cleanup(code=12, file=io.c, line=165): about to call exit(12)

I'll disable compression on my rsync daemon, increase verbosity and see 
how that goes.

>It seems as though something happened in 2.5.6 where
>compression and daemon produce this.  My impression is that
>it doesn't happen via ssh nor without compression.  So far
>we don't have a test case nor have any of the developers
>experienced it.  You may want to try cvs where some of the
>io routines have been changed.
>

I've been running rsync as a client without --compress; is it still 
likely to be caused by compression?

I'll think about trying cvs to see if that helps; right now, I'm trying 
not to introduce too many variables at a time.