I ended up scrapping the whole thing and using somebody elses rsync command, I'll paste in the command I'm using now that does work. Also, this is on a Mac, with rsync version 2.6.3 protocol version 28
rsync -e 'ssh -i $HOME/.ssh/id_rsa -l root' -azxH --numeric-ids --include-from=$HOME/.rsync/backup --partial --partial-dir=.rsync-partial --stats --delete --link-dest=../$wday $HOME 10.0.1.127::rsync/current This works great for whatever reason. I really just gave up trying to understand why. I will say this though, the reason I switched from using 10.0.1.1217:: to 10.0.1.127: in my first email was because I got all sorts of permissions errors so I junked that and started using the latter. Anyway thanks :) --Nathan ----- Original Message ---- From: Matt McCutchen <[EMAIL PROTECTED]> To: Nathan <[EMAIL PROTECTED]> Cc: rsync@lists.samba.org Sent: Thursday, August 10, 2006 5:14:10 PM Subject: Re: Rsync --link-dest over ssh not working On 8/1/06, Nathan <[EMAIL PROTECTED]> wrote: > sudo rsync --dry-run -e 'ssh -l root' --delete -auE \ > --link-dest=../backup.0 \ > /Users/frizop/ \ > 10.0.1.127:/home/rsync/Laptop-Backup/backup.1/ > > What happens is rather then check backup.0, it picks up /root (on the remote > side) as the dest and wants to wipe out everything in there. Your command looks correct. Rsync would try to wipe out /root if the destination filesystem path (following 127:) got cut off, but I don't see how this would happen. What version of rsync are you using on each side? You mention -E: is Mac OS X involved? I recommend that you pass -vvv for triple verbosity and send the output to a file. If you don't see what's wrong, I would be happy to take a look at the output. Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
