IF someone has already solved this please point in right direction. I could find in a search.

This works great but you have to login to the computer remotely to make it work. I would like to CRON the whole thing. I have never been able to find a fix. Thanks to all. (Shared keys have never worked on these boxes.)

---------------------------
IPREMOTE=`host XXXXX.homelinux.com |awk '{print $4}'`
export IPREMOTE
echo Remote: ${IPREMOTE}

expect -c 'spawn rsync -vaz /home/iscuser1/ -e ssh user1@$::env(IPREMOTE):/home/user1/backup/ ; expect a password ; send "12345678\n" ; interact'

Using shared keys is the solution for unattended rsyncs. So why did they "never work"?

jlinkels

1 members found this post helpful.

2 of us tried and notta. I am hatchet programmer, the other guy expert. Even trying to 2 different boxes.

What did you do exactly? A simple ssh-keygen then ssh-copy-id user@remote-host should work.
Then : rsync user@remote:/path/to/source /path/to/backup or rsync /path/to/source user@remote:/path/to/backup.
Just be careful that you setup the cron with the same user.

I can't remember what we did but the key exchange did NOT work; so I need a different approach.

The "expert" needs to figure out why.
Once he does that, your "approach" becomes that much more robust.

Thanks but no help.

Five Minutes to a More Secure SSH
Surely, your "expert" can dedicate 5m to the solution?

Just think, he'll fix the problem and you'll have a lot less coding to do.

I'm done here. Trying to beg you to have your 'expert' fix ssh using keys, and what you expect from this post,
isn't going to end well.

1 members found this post helpful.

It doesn't work for you, but other people get it to work all the time. Which response is more likely to work?

(A) Figure out what you are doing wrong.

or

(B) Try something completely different.

When I was a Linux newbie, I got it to work. It's not that hard. Keep at it. You'll be glad you did.

1 members found this post helpful.

Removed message.