Re: link-dest question revisted

On Thu 01 Jul 2010, d...@safeport.com wrote: > In checking inodes I can find many files that did not change on the > server. E.g.: > > artemis:/mnt# diff 201003/newharbor/home/allvid/allvid.tgz > 201007/newharbor/home/home/allvid/allvid.tgz > artemis:/mnt# ls -il 201003/newharbor/home/allvid/all

link-dest question revisted

I asked a question about not link-dest not creating hardlinks and got ideas and hints that led to the solution which is the link-dest dir must/should be relative to the destination and/or the destination must be empty. I did both and that works fine. My question is what would cause rsync to co

Re: link-dest question

On Tue, 5 Jan 2010, Wayne Davison wrote: On Mon, Jan 4, 2010 at 12:33 PM, wrote:  rsync -vaxH --numeric-ids --delete --exclude=/home/apache/logs \   --link-dest=/mnt/200912/newharbor/home -e ssh newharbor.safeport.com:/home \   201001/newharbor/home/ Is that newharbor/home/

Re: link-dest question

On Mon, Jan 4, 2010 at 12:33 PM, wrote: > rsync -vaxH --numeric-ids --delete --exclude=/home/apache/logs \ > --link-dest=/mnt/200912/newharbor/home -e ssh newharbor.safeport.com:/home > \ > 201001/newharbor/home/ > Is that newharbor/home/home dir really desired? Without a trailing slash on

Re: link-dest question

On Mon 04 Jan 2010, d...@safeport.com wrote: > > The command works but copies all files, i.e. no hard links created. > > rsync -vaxH --numeric-ids --delete --exclude=/home/apache/logs \ >--link-dest=/mnt/200912/newharbor/home -e ssh newharbor.safeport.com:/home > \ >201001/newharbor/ho

link-dest question

The command below was run on FreeBSD 7.2 with rsync-3.0.3. The command works but copies all files, i.e. no hard links created. rsync -vaxH --numeric-ids --delete --exclude=/home/apache/logs \ --link-dest=/mnt/200912/newharbor/home -e ssh newharbor.safeport.com:/home \ 201001/newharbor/ho