various "rsync: connection unexpectedly closed" errors on debian

[wearitdown at myrealbox.com]

>> 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:
>
> Check the rsync log file. That is where the error message will be.


Hi.  Okay, on the server I am downloading from, it shows the following 
(doesn't seem very detailed, if more details are needed, how do I ask 
the admin to increase it?):

    2003/06/21 18:07:03 [2020] rsync: name lookup failed for
    203.208.246.57: Name or service not known
    2003/06/21 18:07:04 [2020] rsync on gentoo-portage/ from UNKNOWN
    (203.208.246.57)
    2003/06/21 18:12:16 [2020] rsync error: timeout in data send/receive
    (code 30) at io.c(103)

Whereas on my client, it shows something like this (this clip not taken 
from the same session, but likely to be similar).

    [snip]
    x11-wm/xpde/xpde-0.3.0.ebuild is uptodate
    generate_files phase=1
    rsync: connection unexpectedly closed (1657342 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 (1493478 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)

Not being much of a programmer, I can only hazard a guess that something 
in io.c on the server and client don't agree, possibly due to a mistake 
on my part.  (The server in this case ran "/usr/bin/rsync --daemon 
--no-detach --safe-links --compress --timeout=1800", but I definitely 
ran without -z or --compress on my client, so compression should not 
have been enabled, right?)