On 12/08/2018 15:34, Martin Gregorie wrote:
> On Sun, 12 Aug 2018 15:00:57 +0200, A. Dumas wrote:
>
>> On 12-08-18 14:08, Martin Gregorie wrote:
>>> I think so. When rsync gets to the file, it realises what it last
>>> backed up as a file is now a directory, so it replaces the file with
>>> the directory and its contents.
>>
>> No, what I'm saying is that normally it doesn't, at least not how I use
>> it, with -au options. For me, that results in an error message "Unable
>> to copy [etc]" or similar and that subtree being skipped. So either you
>> use other (--delete-etc?) options, or maybe with only -a (without -u)
>> rsync will replace instead of skip. Idk, haven't tested the exact
>> implications of rsync options recently.
>>
> I use a different set of options, because we have slightly different
> requirements: I don't want rsync to stop except for serious errors.
> I'm running with these options:
>
> -avzE --delete --delete-excluded --ignore-errors --log-file=$log
>
> plus several excludes so it doesn't back up stuff pseudo-filestore
> structures like /run and /proc
>
>

-x will stop it crossing filesystem boundaries, thus excluding /run
/proc /dev /sys (and others) automatically.


--

Chris Elvidge, England

--- SoupGate-Win32 v1.05