I'm just not entirely clear from the man page.. does the timeout start
counting from the last communication, or does it start counting from the
beginning of the transmission?
also, if the server is set to timeout at, say, 300s, and it's busy
moving stuff around but not talking to the client, d
Wayne Davison wrote:
On Sat, Jul 08, 2006 at 08:07:43AM -0700, Eric Horne wrote:
It seems that once the transfer is complete, --delay-updates takes a
really long time to copy data.
The only file movement that --delay-updates supports is renaming -- it
never re-copies the files
Hi. I'm running rsync 2.6.8 at two sites with --partial/--partial-dir
and --delay-updates enabled.
It seems that once the transfer is complete, --delay-updates takes a
really long time to copy data. From strace output, it looks like it is
actually re-reading the data out of the .rsync-partial
Matt straightened me all out, thanks again.
Using -K -L did exactly what I wanted it to do. Now I just need to get
it to work with remotes that aren't at 2.6.3 or above (think I'll be
upgrading those) :)
-Eric
Matt McCutchen wrote:
On Tue, 2005-12-20 at 13:53 -0800, Eric H
k, and was left with the same behaviour -- that the symlink turns
into a directory.
So I think I'm still stuck (or I misunderstood what you said)
-Eric
Matt McCutchen wrote:
On Tue, 2005-12-20 at 11:40 -0800, Eric Horne wrote:
rsync -rlptDvzL --stats --include=a/ --include=a/dir/
--includ
I'm running 2.6.6 on a red hat EL3 system.
using the following command,
rsync -rlptDvzL --stats --include=a/ --include=a/dir/
--include=a/dir/symlink/ --include=a/dir/symlink/dir2/
--include=a/dir/symlink/dir2/dir3/ --exclude='**' /export/stuff
remote::stuff
I expect the "symlink" (which is
I'm trying to rsync a directory structure and it's contents to another
machine. I want to make sure that the entire toplevel part of the
directory structure is created at the remote site, since it may not exist.
top: A/ B/ C/
under B/: 1/ 2/ 3/
under 2/: x/ y/ z/
all of this is located in /t
