On 5/8/07, Brent Thompson <[EMAIL PROTECTED]> wrote:
Often we need to preserve the information atime conveys, but I have found
no way to get rsync to preserve this, nor any hint it is being worked on.
It would be great if 'rsync -t' also set atime not just mtime -- or maybe a
new option is desire
Often we need to preserve the information atime conveys, but I have found
no way to get rsync to preserve this, nor any hint it is being worked on.
It would be great if 'rsync -t' also set atime not just mtime -- or maybe a
new option is desired for atime.
I don't know if the -X mentioned in "NEWS
On Tue, May 08, 2007 at 09:49:05AM -0700, Wayne Davison wrote:
> The summary description could use an extra mention, though.
You can read the very latest manpage with my improvements here:
http://rsync.samba.org/ftp/rsync/nightly/rsync.html
E.g., there's extra quick-check discussion in the DESCR
On Tue, May 08, 2007 at 03:45:40PM +0300, Atte Peltomaki wrote:
> Forgets to say that "efficient checksum-search algorithm" is not enabled
> by default *doh*.
Untrue. The checksum-search algorithm is enabled, just the pre-transfer
checksum check is not. Those are two different things.
The "qui
You need to supply the --checksum option if you want to make sure
that the contents are indeed identical. This is normally not done
as that would cause a massive IO load; cases that size and
timestamp are identical but not the contents don't usually
happen...
The manual is indeed not very clear
On Tue, May 08, 2007 at 01:07:51PM +0200, Paul Slootman wrote:
> On Tue 08 May 2007, Atte Peltomaki wrote:
> > Source:
> >
> > md5sum:
> > 2ac4a4ad88da17f49d26c9e578ce5432 somefile.exe
> > sha1sum:
> > eaabb30b716e993be000b89208e2d9f63e78f052 somefile.exe
> > ls -l:
> > -rwxrw 1 user group
On Tue 08 May 2007, Atte Peltomaki wrote:
>
> I'm seeing a weird problem with rsync 2.6.9 protocol version 29 on
> Debian Sarge. When copying a file from one location to another between
> two Debian boxes, if destination includes a file with same size and
> name, rsync fails to see that they are n
Hi,
I'm seeing a weird problem with rsync 2.6.9 protocol version 29 on
Debian Sarge. When copying a file from one location to another between
two Debian boxes, if destination includes a file with same size and
name, rsync fails to see that they are not exactly the same file.
The situation origina