Re: which rsync command?

2017-02-23 Thread Francis . Montagnac
On Fri, 24 Feb 2017 07:51:56 +0100 francis.montag...@inria.fr wrote: >> Unfortunately, the output from —dry-run is still likely to be >> sufficiently extensive that looking over it won’t be a completely >> certain test. > Then redirect to a file and grep deleting in this file. Given the

Re: which rsync command?

2017-02-23 Thread Francis . Montagnac
On Thu, 23 Feb 2017 18:07:20 + David Epstein wrote: > I will try the modification > rsync --dry-run -avi --delete --filter 'protect /*’ --filter ‘protect /.*’ > SOURCE/ TARGET/ The 'protect /.*’ is useless: unlike the shell, rsync interprets * simply as a path component, regardless thus

Re: which rsync command?

2017-02-23 Thread Kevin Korb
Either solution should work fine. Your dry run results should be the same. -v and -i are only output modifying options they don't actually change the way that rsync works. The extra string there is explained in the --itemize-changes section of the man page but that particular one means that the

Re: which rsync command?

2017-02-23 Thread David Epstein
This is looking good and very helpful to an rsync novice. I will try the modification rsync --dry-run -avi --delete --filter 'protect /*’ --filter ‘protect /.*’ SOURCE/ TARGET/ and see what it produces. I do have a number of directories and files beginning with a dot in TARGET and these need

Re: which rsync command?

2017-02-23 Thread Francis . Montagnac
Hi. On Thu, 23 Feb 2017 11:07:16 -0500 Kevin Korb wrote: > I hate to say it because it goes against my normal advice but this is > one instance where using a * in the source parameter would help... I totally agree. I thing that using a protect filter achieves this goal (without using a *

Re: which rsync command?

2017-02-23 Thread David Epstein
Thanks for the helpful advice. In view of the conflicting advice from Joe and Kevin I tried creating a couple of very small directories test1 and test2, to see what happens when the rsync command rsync -avi —dry-run test1/ test2/ is given. I was pleased to see that —dry-run does explicitly say

Re: which rsync command?

2017-02-22 Thread Joe
I'm probably missing something, but it looks like your first requirement rules out using --delete, but your third requirement seems to imply the need for it because you want the source and target to be identical - and it won't be if there are any files on the target which are not on the source.

Re: which rsync command?

2017-02-22 Thread Kevin Korb
You should be fine as long as you don't add --delete. I would start with rsync -vai --dry-run SOURCE/ TARGET/ Add whatever the OSX specific option is (I think -E) Yes, --dry-run shows you what it would have done without --dry-run and yes, if you can't read all the files then you need to run it

which rsync command?

2017-02-22 Thread David Epstein
All the files and directories I want to talk about are on the same machine (a Mac). I have a directory that I will call SOURCE. This contains a a number of files, some of which are directories containing further files. I want to copy these files to another directory, which I will call TARGET.