don't get interrupted during a sleep.

cause recursive error messages)

rsh relies on stdin being blocking
ssh relies on stdout being non-blocking

what we've done before is to set both stdin and stdout to either
blocking or non-blocking. Now I set stdin to blocking and stdout to
non-blocking. This seems to fix all cases I've tested.

it looks like ssh is willing to accept a non-blocking fd when used as
a transport, this seems to avoid the Solaris socketpair bug

section on exclude/include was supposed to be about "+/-" so I changed
the statement to "Here are some exclude/include examples".

because I have an obscure system (Amdahl's UTS 2.1.2) in which socketpair()
exists but is broken.

the functions, especially "socketpair" so that socket-related functions will
be properly discovered on SVR4-based systems such as Solaris.  Problem
discovered by Kenji Miyake <kenji@miyake.org>

deleted after being backed up in a rename operation

these with socketpairs. The receiver now sleeps until it gets a signal
to tell it to exit

also fixed test.sh to use the current version remotely

with the new error handling code it is possible for rsync to get stuck
on the final transaction, leaving it hung.

looks like 2.4.1 will be pretty soon

the last pre-release had a bug that didn't setup the multiplexing
correctly. This means that pre-release will get "unexpected tag -7"
whenm talking to the fixed code.

its all too common to compile with a working libc and run on a broken
one.

  connections (this fixes the stderr/stdout problem). Upped
  protocol version for backward compat
- use multiplexing on error fd
- upped minimal protocol version
- got rid of some ugly code in the write buffering

ssh clag problems as long as you also fix the same problem in sshd

removed all the old read buffering code from io.c as this was only
there to try to reduce the chance of clagging up sshd.

(was a minor bug in send_file_list)

cross-filesystem

my system the LIBC tests meant it never compiled and we used the
broken system one.

hacked it so it does compile

when using --progress

of memory vs. ssh bugs. uggh.