Re: Error with paths with ()'s

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If you want find to generate your list use --files-from: find . -type f -atime -1 -print0 | rsync -aP --files-from=- --from0 . 10.0.0.11:/Volumes/Drive5/ On 08/17/2015 02:13 AM, @lbutlr wrote: > I was trying to process a bunch of folders to sync them

Re: Error with paths with ()'s

On Aug 17, 2015, at 4:05 AM, Kevin Korb wrote: > If you want find to generate your list use --files-from: > > find . -type f -atime -1 -print0 | rsync -aP --files-from=- --from0 . > 10.0.0.11:/Volumes/Drive5/ This works: find . -type f -atime -1 -exec rsync -aP {} /Drive5/{} This fails if ther

Re: Error with paths with ()'s

I haven't used rsync with networks, but I do use bash a lot. First, let me state the obvious. It looks like your code is executing rsync in a bash one liner once for each file that find returns. That's not cool! And it's almost definitely not what you wanted to do. Among other things, that me

Re: Error with paths with ()'s

On Aug 17, 2015, at 3:06 PM, Joe wrote: > First, let me state the obvious. It looks like your code is executing rsync > in a bash one liner once for each file that find returns. That's not cool! > And it's almost definitely not what you wanted to do. It is perfect;y acceptable and definitely ‘c

Re: Error with paths with ()'s

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Remember that when you rsync to 10.0.0.11:/Drive5/{} rsync is going to run: 'ssh 10.0.0.11 rsync --server /Drive5/whatever file name(s) were in {}' You should see the problem now. Even if the spaces and parentheses are quoted or escaped the ssh adds

Re: Error with paths with ()'s

On Sun, Aug 16, 2015 at 11:13 PM, @lbutlr wrote: > find . -type f -atime -1 -exec rsync -aP {} 10.0.0.11:/Volumes/Drive5/{} > \; > The use of "{}" on the receiving (remote) side is superfluous -- just specifying a destination dir (your .../Drive5/ path) is enough for rsync to use the same name a

Re: Error with paths with ()'s

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It is true that you don't need the {} in the remote arg but due to the syntax you probably want --relative instead. On 08/17/2015 07:03 PM, Wayne Davison wrote: > > On Sun, Aug 16, 2015 at 11:13 PM, @lbutlr > wrote: > > fi