Re: rsync question

Hi Another rather recent feature of "rsync -R" (--relative) is to easily allow to specify from what point you want -R to apply. From the man: -R, --relative ... It is also possible to limit the amount of path information that is sent as implied directories for each path you specify.

Re: rsync question

On Mon, Jul 13, 2020 at 7:51 PM Tim via users wrote: > On Mon, 2020-07-13 at 16:37 +0200, Tom H wrote: >> >> The trailing slash only matters for the source directory. >> >> I think of the trailing slash for "cp" on *BSD (and macOS) and >> "rsync" as meaning "/*"... > > Does it matter anywhere?

Re: rsync question

On Tue, 2020-07-14 at 03:20 +0930, Tim via users wrote: > On Mon, 2020-07-13 at 16:37 +0200, Tom H wrote: > > The trailing slash only matters for the source directory. > > > > I think of the trailing slash for "cp" on *BSD (and macOS) and > > "rsync" as meaning "/*"... > > Does it matter

Re: rsync question

On Mon, 2020-07-13 at 16:37 +0200, Tom H wrote: > The trailing slash only matters for the source directory. > > I think of the trailing slash for "cp" on *BSD (and macOS) and > "rsync" as meaning "/*"... Does it matter anywhere? I've always put one on the end of directory filepaths, just for my

Re: rsync question

On Mon, 2020-07-13 at 20:39 +1000, Cameron Simpson wrote: > Still this makes an unwanted subdirectory (unwanted to me, most of the > > time). I still prefer the both-src-and-dst-exist approach an to use a > > trailing slash: > > > > rsync -ia A/ B/ > > > > which just replicates the

Re: rsync question

On Mon, Jul 13, 2020 at 12:26 PM Patrick O'Callaghan wrote: > On Mon, 2020-07-13 at 19:20 +1000, Cameron Simpson wrote: >> >> Make two directories the same: >> >> rsync path/to/A/ other/path/to/B/ >> >> (no bare names after the final '/'). > > I don't think the trailing slash matters on the

Re: rsync question

On 13Jul2020 11:25, Patrick O'Callaghan wrote: >On Mon, 2020-07-13 at 19:20 +1000, Cameron Simpson wrote: >> Make two directories the same: >> >> rsync path/to/A/ other/path/to/B/ >> >> (no bare names after the final '/'). > >I don't think the trailing slash matters on the destination

Re: rsync question

On Mon, 2020-07-13 at 19:20 +1000, Cameron Simpson wrote: > Make two directories the same: > > > > rsync path/to/A/ other/path/to/B/ > > > > (no bare names after the final '/'). I don't think the trailing slash matters on the destination directory. At least that's not what the man page

Re: rsync question

On 12Jul2020 16:06, bruce wrote: >assume > >/home/test/user1/foo >/var/www/html > >a user is in the "/" dir > >how can this user copy/rsync "foo" dir to get /var/www/html/foo > >i know you could cd to /home/test/user1 and >do >rsync -vv -aR foo/ /var/www/html/ > >which would get

Re: rsync question

Hi. On Sun, 12 Jul 2020 16:06:00 -0400 bruce wrote: > assume > /home/test/user1/foo > /var/www/html > a user is in the "/" dir > how can this user copy/rsync "foo" dir to get /var/www/html/foo > i know you could cd to /home/test/user1 and > do > rsync -vv -aR foo/ /var/www/html/ Simply

rsync question

assume /home/test/user1/foo /var/www/html a user is in the "/" dir how can this user copy/rsync "foo" dir to get /var/www/html/foo i know you could cd to /home/test/user1 and do rsync -vv -aR foo/ /var/www/html/ which would get /var/www/html/foo but doing an rsync to a specific target

Re: rsync question?

For all who replied! Thanks for taking a few mins to read/reply. I had seen the -"-rsync-path" running the "mkdir" cmd being used for running the mkdir on the remote side. My case was definitely looking to copy files locally between a Source and Destination Dir. So, I was looking to implement

Re: rsync question?

On Tue, 2020-06-23 at 11:08 -0400, bruce wrote: > I'm looking to copy from sourceDir to targetDir where the entire > targetDir (parents) doesn't exist. So I'm trying to rsync and create > the dir path at the same time. I quick google search for: rsync create parents produced this:

Re: rsync question?

On 23Jun2020 11:57, bruce wrote: >Ok... >More testing.. >Opened up the dir perms to 775 -- just to see if this was/is an issue. You'd get a permission error if that were the issue. (There are scenarios where permissions can produce no-such-file-or-dir, but they are to do with not being able to

Re: rsync question?

Just a thought had you tried with... 1) Allcute, backtick, left quote, or an open quote, the back quote or backquote is a punctuation mark (`). It's on the same U.S. computer keyboard key as the tilde. 2) double quote(") In placecof single quotes ? Regards Bimal Kumar On Tue, 23 Jun 2020,

Re: rsync question?

Ok... More testing.. Opened up the dir perms to 775 -- just to see if this was/is an issue. I can successfully do mkdir -p /home/webdev/composer/vendor/laravel with the /home/webdev dir being empty. This creates the dir path However, running the rsync cmd, still generates the error: rsync

Re: rsync question?

On Tue, Jun 23, 2020 at 11:17 AM Jamie Fargen wrote: > > Bruce- > > Try rsync -av /home/test/.config/composer/ /home/webdev/composer/ Hi Jamie... I don't want to use this as the sourceDir >> "/home/test/.config/composer/" It's got other dirs/files.. which is why I used the sourceDir here.. >>

Re: rsync question?

Bruce- Try rsync -av /home/test/.config/composer/ /home/webdev/composer/ Regards, -Jamie On Tue, Jun 23, 2020 at 11:09 AM bruce wrote: > Hey. > > I've got a test scenario. I'm looking to copy from sourceDir to > targetDir where the entire targetDir (parents) doesn't exist. So I'm > trying to

rsync question?

Hey. I've got a test scenario. I'm looking to copy from sourceDir to targetDir where the entire targetDir (parents) doesn't exist. So I'm trying to rsync and create the dir path at the same time. I've tried to play with variations of the following and I'm missing something.. rsync -aq

Re: rsync question

On 11Feb2018 16:40, Samuel Sieb wrote: On 02/10/2018 09:16 PM, Cameron Simpson wrote: On 10Feb2018 20:50, Robert Nichols wrote: On 02/10/2018 12:31 PM, bruce wrote: Got it.. or think I do.. It appears the -I --ignore-times  attribute will

Re: rsync question

On 02/10/2018 09:16 PM, Cameron Simpson wrote: On 10Feb2018 20:50, Robert Nichols wrote: On 02/10/2018 12:31 PM, bruce wrote: Hey... Got it.. or think I do.. It appears the -I --ignore-times  attribute will essentially force a redo of any/all files in the rsync...

Re: rsync question

On 10Feb2018 20:50, Robert Nichols wrote: On 02/10/2018 12:31 PM, bruce wrote: Hey... Got it.. or think I do.. It appears the -I --ignore-times attribute will essentially force a redo of any/all files in the rsync... Actually it will do the opposite. With the

Re: rsync question

On 02/10/2018 12:31 PM, bruce wrote: Hey... Got it.. or think I do.. It appears the -I --ignore-times attribute will essentially force a redo of any/all files in the rsync... Actually it will do the opposite. With the "-I" flag, rsync will ignore differences in modification times as a

Re: rsync question

On Sat, 2018-02-10 at 13:31 -0500, bruce wrote: > I'm interested in examining the list as the files are transferred.. rsync -v ... (more than one -v gives more verbosity) poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send

Re: rsync question

Hey... Got it.. or think I do.. It appears the -I --ignore-times attribute will essentially force a redo of any/all files in the rsync... I'm interested in examining the list as the files are transferred.. thanks On Sat, Feb 10, 2018 at 12:48 PM, Richard

Re: rsync question

> Date: Saturday, February 10, 2018 12:16:47 -0500 > From: bruce > > Given all the attributed for rsync... > > Is there an attribute or approach to allow/force rsync to redo a > "complete" xfer of files..? > > I'm sure there is but I must be missing it.. The issue(s)

Re: rsync question

On Sat, 10 Feb 2018 12:16:47 -0500 bruce wrote: > Is there an attribute or approach to allow/force rsync to redo a > "complete" xfer of files..? I'm not aware of a way, and it makes sense. If the identical file is already there, why would rsync spend the resources to

rsync question

Hey! Given all the attributed for rsync... Is there an attribute or approach to allow/force rsync to redo a "complete" xfer of files..? I'm sure there is but I must be missing it.. thanks.. ___ users mailing list -- users@lists.fedoraproject.org To

rsync question -

Is rsync not supposed to append to the existing files or just copy over them? I would like to update /home/bobg/.thunderbird but the following simply overwrites everything: [root@box10 bobg]# rsync -avz /mnt/HOME1/bob/TBdBx07/ /home/bobg/.thunderbird/ In this case I have rsynced

Re: rsync question -

On 11/15/2013 09:17 AM, Bob Goodwin - Zuni, Virginia, USA issued this missive: Is rsync not supposed to append to the existing files or just copy over them? I would like to update /home/bobg/.thunderbird but the following simply overwrites everything: [root@box10 bobg]# rsync -avz

Re: rsync question -

On 15/11/13 12:53, Rick Stevens wrote: No, you're not misunderstanding it. rsync looks at the source and target and if there are differences, it copies from the source to the target. In your case, you told rsync to copy everything inside the /mnt/HOME1/bob/TBdBx07 directory (the source) to the

Re: rsync question -

On 15Nov2013 17:19, Bob Goodwin bobgood...@wildblue.net wrote: Ok that appears to have done what I wanted, at least it transferred a lot less data in very little time. One thing I think Rick may have missed out is that if a file is similar on the target (eg it had just grown on the source,