opening an inbound socket, we might get several address results,
e.g. for the machine's ipv4 and ipv6 name.

If binding a wildcard, then any one of them should do.  If an address
was specified but it's insufficiently specific then that's not our
fault.

However, some of the advertized addresses may not work because e.g. we
don't have IPv6 support in the kernel.  In that case go on and try all
addresses until one succeeds.

many globals already.

Better error messages for network-related failures.

because on Solaris (for one) it's not in libc.

seems no point using anything but the platform's native definition,
and if we can't get that from the system headers we're hosed anyhow.

how this is supposed to help.

Check for netdb.h

be conditional -- they are missing on e.g. Solaris.  Not sure if this
will fix it.

Show IPv6 availability in --version.

or literal IP addresses to rsync, and if your platform supports them
they will be used.  Also there are -4 and -6 command-line options to
choose the default address type.  Thankyou!

readlink_stat() on an excluded file can be a problem when using the
--copy-links option (also known as -L) and the excluded file is a symlink
that points nowhere.

the generator can easily make no progress for a long time, so don't do
timeout processing checks

a test for the screwup and disables largefile support

only the attributes of files that rsync is meant to synchronize.

Test cases should depend on testing tools.

only the attributes of files that rsync is meant to synchronize.