trying to write. This guarantees that the maximum amount of data that
can be written at any one time is written.

temporary files were being created with the same permissions as the
original file. So if the file was setuid but not owned by the user
doing the transfer then there was a window of opportunity for a
malicious user to execute it with the wrong permissions while it was
being transferred.

Thanks to snabb@epipe.fi for pointing this out.

print the file name.

get removed by chown calls.

algorithm.

workaround for buggy systems that say there is space to write when
there isn't.

This bug resulted in rsync being much less efficient that it could be
for files with more than 64k blocks. With the adaptive block size code
giving a maximum block size of 16k this means that files larger than
1GB were handled very inefficiently. The transfer was still accurate,
just slow.

the block size.

printed when redirecting output to a file.

unsigned comparisons. Transferring files between two machines that
treated strcmp() differently led to the files being given the wrong
name at the destination if the filenames had characters > 128 (such as
Kanji characters) and the source and destination machines treated
strcmp() differently (ie. one treated strings as signed and the other
as unsigned).

We now treat all string comparisons for file list sorting as unsigned.

reset offset to 0 at the start of each loop so the filenames get
printed correctly when sending directories followed by local names.

a writefd_unbuffered call!

this should fix the "decompressor lost sync" bug

are faster and don't cause problems in a chrooted environment on any
systems.

get out of sync.

from a rsync server

it is a power of 2.

- handle start of line in exclude properly

we no longer use non-blocking IO, instead it uses select a lot more,
being careful to always allow for reading whenever a valid read fd is
available and chcking timeouts.

also split the file io calls into fileio.c