>
> That is as documented. You are requesting that the directory is synced
> to c, preserving all attributes (due to -a) so rsync does that.
>
Ah... the attributes of the containing directory are transferred to the
containing directory on the destination.
I read that but failed to absorb it.
When you rsync a directory, say `$rsync mydir/ ...` with the trailing
slash, the destination directory is changed to the ownership,
permissions and timestamp of `mydir`.
Consider this simple example
$ mkdir test
$ cd test
$ mkdir a b
$ touch -d '01 jan 1980' a/A
$ touch -d
On 20/09/16 12:21, John Lane wrote:
> I can use --link-dest multiple times for backups so that files affected
> by a backup-delete-backup-replace-backup scenario get linked. It works well.
>
> However, consider this scenario: backup-modify-backup-undo-backup. We have
>
> * back
On 29/10/16 03:14, Wayne Davison wrote:
> If you want to pass non-rsync args (etc) you should be using
> --rsync-path. The -M option is only for sending rsync-related options.
Ok, so instead of
$ rsync -av -M --customarg1=value1 -M --customarg2=value2 file1 file2
user@server:some/path
I can do
Hello, I asked the below back at the beginning of August but have
received no replies. If anyone can help me with this problem it would be
much appreciated. If I have not provided some necessary information then
please let me know so I may do so. Thanks in advance.
> I have been working on a
I can use --link-dest multiple times for backups so that files affected
by a backup-delete-backup-replace-backup scenario get linked. It works well.
However, consider this scenario: backup-modify-backup-undo-backup. We have
* backup 1 contains file 'a'
* backup 2 contains file 'a' ( with
I have been working on a backup server where I have a server-side script
that wraps the server-side rsync invocation. I have used the client-side
rsync -M (--remote-option) to send options to the server script,
removing them from the command-line prior to invoking the server-side
rsync. This was
