In article <055b01c0c11f$d32f4010$6e0b4b89@munich>,
David Salisbury <[EMAIL PROTECTED]> wrote:
>Thanks Ian. I was surprised the question seeded the discussion
>that it did. You are "spot on" below on what I'm trying to do, and have
>used
>the method you describe below to basically emulate an rsh command. But
>either my question was too vague or I'm missing something basic.
>
>What you discribed below is essentially a secure, passwordless, rsh command.
>But doesn't rsync *itself* use ssh to make the connection in order to
>compare
>the two files and directory structures?!??! Or, does it use it's own port
>or something?
>
>If I can issue this ssh command without a passwd....
>
> ssh -x -l some_user some.domain.com 'some command, (which i won't need for
>rsync)';
>
>then how can I make rsync use this ability for it's
>connection?! Do I need to hack the source for this sort of thing? Ugh.
I don't see the problem. It should "just work". (So long as you pass
"-e ssh" to rsync.) If the above ssh command works without a password,
then the corresponding rsync command:
rsync -e ssh [EMAIL PROTECTED]:/path /path2
should also work without a password, in the same environment.
But note that if the *reason* the ssh command runs without a password
is that there's a user logged in to an ssh-agent, which is supplying
a key, then the rsync won't necessarily work unattended. If you want
unattended access, you need to make a dedicated (and unprotected)
ssh key, as I outlined in my previous message.
- Ian
