Greetings,
I applied the atimes.diff patch from the rsync-patches file from the
rsync download page, but it seems not to be working: the original
file access times of copied files are not preserved. Does this patch
work correctly for someone?
Regards,
A. Berger.
--
Please use reply-all for
Thanks!
On Mon, Mar 28, 2016 at 08:49:09AM -0400, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> My guess is that it is the atimes patch causing the problem. Normally
> rsync would never say "u" in the itemized output as it is "reserved
> for future use". Plus copying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My guess is that it is the atimes patch causing the problem. Normally
rsync would never say "u" in the itemized output as it is "reserved
for future use". Plus copying the file would change the atime.
On 03/28/2016 08:44 AM, Albert Berger wrote:
>
On Mon, Mar 28, 2016 at 08:11:07AM -0400, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> What does --itemize-changes say about these files?
>
> Also, what is --atimes? Is this the Apple modified rsync for OSX?
>
> On 03/28/2016 07:51 AM, Albert Berger wrote:
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What does --itemize-changes say about these files?
Also, what is --atimes? Is this the Apple modified rsync for OSX?
On 03/28/2016 07:51 AM, Albert Berger wrote:
> Greetings,
>
> when the daily system backup with rsync is performed, thousands of
>
Greetings,
when the daily system backup with rsync is performed, thousands of files (e.g.
from /usr directory),
which are not modified are uselessly transferrred to the backup storage every
day.
The rsync command is the following:
rsync --update -DHAErlptgo --relative --atimes --delete-during
Hi,
On Sun, Mar 27, 2016 at 06:39:53PM -0700, drsalists wrote:
>
> You could probably use CIFS, NFS or sshfs. ??It wouldn't be as fast, but the
> memory requirements should be less.
Sorry, I don't understand how to sync over NFS or sshfs without rsync. Can
you explain this please? I don't want
