- 23 Nov, 1999 1 commit
-
-
Andrew Tridgell authored
this makes sure that the write never blocks.
-
- 15 Nov, 1999 1 commit
-
-
Andrew Tridgell authored
io.c). Thanks to Theo for pointing out this brokenness.
-
- 08 Nov, 1999 4 commits
-
-
rsync-bugs authored
-
Andrew Tridgell authored
-
Andrew Tridgell authored
copy. This makes us match GNU cp more closely.
-
Andrew Tridgell authored
andrewdagger@xerox.gbr.com) added note about multiple excludes per exclude option
-
- 04 Nov, 1999 1 commit
-
-
David Dykstra authored
so the check for dry_run and CHECK_RO are not done when flags is O_RDONLY. Only do the adding of O_BINARY, which was the intention.
-
- 01 Nov, 1999 2 commits
-
-
Andrew Tridgell authored
thanks to Dave for pointing this out.
-
Andrew Tridgell authored
-
- 31 Oct, 1999 6 commits
-
-
Andrew Tridgell authored
preserve_perms is off.
-
Andrew Tridgell authored
-
Andrew Tridgell authored
it is equivalent to --partial --progress
-
Andrew Tridgell authored
-
Andrew Tridgell authored
-
Andrew Tridgell authored
-
- 27 Oct, 1999 1 commit
-
-
Andrew Tridgell authored
working correctly.
-
- 25 Oct, 1999 1 commit
-
-
Andrew Tridgell authored
and O_BINARY
-
- 19 Oct, 1999 1 commit
-
-
David Dykstra authored
Suggested by Roger Price <rprice@cs.uml.edu>
-
- 06 Sep, 1999 1 commit
-
-
Andrew Tridgell authored
-
- 30 Aug, 1999 1 commit
-
-
Andrew Tridgell authored
from Bob Edwards
-
- 09 Jul, 1999 2 commits
-
-
David Dykstra authored
One is a note that a leading "/" in a symlink target will not behave exactly as if a chroot had occurred, but I decided it wasn't worth the making it the same. The other is note about an extra harmless trailing "." that is added under some rare circumstances.
-
David Dykstra authored
1. The file paths being sent and received were not "sanitized" to ensure that there weren't any ".." components that would escape the top level directory. This can't happen with the standard rsync client, but it could be exploited on both read and write if someone modified an rsync client. This fix sanitizes all incoming and outgoing paths when "use chroot = no". 2. If a module is also "read only = no", clients could have created symbolic links with ".." components that would allow writing outside of the module. This could happen with the standard rsync client. This fix sanitizes all incoming symbolic link targets when "use chroot = no". Previously, only top-level paths (anything passed in command line arguments) were sanitized. Sorry, I didn't think about the individual file paths before now.
-
- 27 Jun, 1999 1 commit
-
-
Andrew Tridgell authored
Matti Aarnio)
-
- 26 Jun, 1999 1 commit
-
-
Andrew Tridgell authored
comparing checksums for the --checksum (-c) option.
-
- 13 Apr, 1999 1 commit
-
-
Andrew Tridgell authored
rsync servers via a web proxy (useful for getting through firewalls)
-
- 06 Apr, 1999 9 commits
-
-
rsync-bugs authored
-
Andrew Tridgell authored
catches most sorts of io errors and ensures we report a error in our exit status.
-
Andrew Tridgell authored
-
Andrew Tridgell authored
-
Andrew Tridgell authored
all files have been excluded).
-
Andrew Tridgell authored
1) rsync won't copy directories at all if recursion isn't selected 2) --delete won't do anything if recursion isn't selected
-
Andrew Tridgell authored
rsyncd.conf are not passed to the client and thus only affect the file lists on the server.
-
Andrew Tridgell authored
permissions on directories after a transfer.
-
Andrew Tridgell authored
patch from racke@linuxia.de
-
- 02 Apr, 1999 1 commit
-
-
David Dykstra authored
hadn't changed but its permissions had, the file wasn't copied but its permissions were attempted to be set anyway. Made a change to skip setting the permissions in that case.
-
- 24 Mar, 1999 2 commits
-
-
David Dykstra authored
--compare-dest. It was due to an incomplete analysis of the problem, sorry. I left a comment in its place indicating that normally the parent directories should already have been created. It turned out to actually be a bug in nsbd in which it was not always including all the parent directories in the include list like it was supposed to. The files themselves were still being sent but that was only because my exclude_the_rest optimization was kicking in; if it weren't, excluding the parent directories would have had the side effect of excluding the files too. So it really had nothing to do with the --compare-dest option after all, just with the requirement that if you use --exclude '*' you need to explicitly include all parent directories of files you include.
-
David Dykstra authored
because at that point in the program the umask is set to 0. Now creating the file with mode (666 & ~orig_umask).
-
- 23 Mar, 1999 1 commit
-
-
David Dykstra authored
target destination were not getting created. There was a case in receiver.c to do that but it was only getting invoked when the -R option is specified, although I don't know why it was limited to that. It's too bad I didn't get a chance to more fully test the use of --compare-dest by my nsbd program before releasing rsync 2.3.0. I'll probably need to put a workaround in nsbd too until the next release of rsync.
-
- 15 Mar, 1999 2 commits
-
-
rsync-bugs authored
-
David Dykstra authored
both directions.
-