rsync

NameLast commit messageLast commit date
libChecker showed that zlib was using a element of its internal state structure without initialising it. Although it looks harmless I've added a bzero() to make absolutely sure that the code behaves consistently across platforms.28 years ago
.cvsignoreadded .cvsignore to the .cvsignore file to prevent it from being distributed when I run the release script28 years ago
.ignoreInitial revision30 years ago
byteorder.hInitial revision30 years ago
checksum.cdamn, I had implicitly assumed signed characters when writing the rolling checksum code. The result is that rsync worked much more slowly when going between two machines where one of the machines uses signed and the other unsigned chars. The rolling checksum rarely matched so effectively a copy was done in many cases. The data always came through correctly so no file corruption occurred but it's pretty pointless using rsync if it doesn't speed things up! I've now made the sign of the chars explicit28 years ago
compat.csave some more bytes by making the checksum smaller30 years ago
configure.in*** empty log message ***28 years ago
COPYINGInitial revision30 years ago
exclude.csome people are now using rsync as a public server, using various patches or wrappers. One problem with this is that rsync was not written with this in mind and wasn't very careful about possible stack overflows etc which could lead to security breaches. This wasn't a problem when run in the traditional way as any user that can run rsync can login anyway and cause much more damage that way. This patch attempts to close possible stack overflow problems. I've checked for all strcpy(), strcat(), sprintf() and memcpy() overflows. I would appreciate it if someone else with a devious mind could also go through the rsync source code and see if there are any other stack overflows possible. Let me know if you do.28 years ago
flist.c*** empty log message ***28 years ago
hlink.c*** empty log message ***28 years ago
install-shInitial revision30 years ago
io.c#if 0 the write exception code for the moment. I need to work out why it gets a successful write select on a fd followed by a EAGAIN write yet the fd is still OK.28 years ago
main.c*** empty log message ***28 years ago
Makefile.in- check for setlinebuf() in autoconf. Apparently HPUX doesn't have it - use @exec_prefix@ and @prefix@ in more useful ways in Makefile.in28 years ago
match.cminor cleanups (unused variables etc)28 years ago
md4.c*** empty log message ***30 years ago
md4.hInitial revision30 years ago
mkproto.awkInitial revision30 years ago
README*** empty log message ***28 years ago
rsync.c*** empty log message ***28 years ago
rsync.h*** empty log message ***28 years ago
tech_report.texInitial revision30 years ago
token.ccasting cleanups (rsync now compiles cleanly under IRIX 6.4)28 years ago
util.cadded a --relative (== -R) option. This is what Anthony Thyssen suggested on the list recently. See the man page entry for details but basically it changes the behaviour so that paths are not stripped, thus allowing you to specify a single rsync command to sync lots of directories/files while preserving the full path name of each file. also fixed a bug in the handling of umasks when both the source and destination machines are local. We need to reset the umask before the exec to ensure that the child gets a correct umask.28 years ago
version.hpreparing for release of 1.6.728 years ago