On 7/8/06, Grignon Mickaël <[EMAIL PROTECTED]> wrote:
Will rsync erase the byte in excess on the receiver even if the --delete
option is not set ?
Yes. --delete is only needed to delete entire files, not extraneous bytes.
Wayne, let me suggest the following clarification/fix to the original
d
Hi,
I'm translating the document How rsync works to
understand exactly how rsync works when it finds modified files.
I'm translating "the sender" and I notice a strange fact.
I would like to take an example where a byte
is missing in a file.
In facts :
The generator has created a cheksu
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. Perhaps
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. From strace output, it looks like it is
> actually re-reading the data out of the .rsync-partial directory for
> each file and then
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
On Fri, Jul 07, 2006 at 02:43:27PM -0700, Brett Hamilton wrote:
> rsync: failed to hard-link /Volumes/backups/vanguard/backup.0/dev/agpgart
> with dev/agpgart: Invalid argument (22)
The message "Invalid argument" is from your OS, and it looks like it is
being generated when trying to hard-link a
