On Fri, Jan 05, 2001 at 10:19:34AM -0500, Rick Otten wrote:
> > Yes, the error message is coming because ssh is terminating early but I
> > don't think that the advice that Jason goes on to give (using extra keys,
> > expect, etc) is correct. There is no reason why rsync can't handle a
> > double prompt, because when you use "rsync -e ssh" all the prompting is
> > handled completely by ssh; rsync has nothing to do with it. I just tried
> > an example and it worked ok. Are you getting any other error messages
> > before "unexpected EOF in read_timeout"? My guess is that you aren't
> > getting properly authenticated to ssh. Using "rsync -e 'ssh -v'" may
> > give you more info about what's going wrong.
>
> It looks to me like the second password is being required by the shell rather
> than the ssh authentication mechanism... (sdshell)
That could indeed be a problem because rsync is expecting the first data
over the connection to be coming from its own corresponding executable. I
just tried for example
rsync -e ssh --rsync-path "echo 'prompt: ';/path/to/rsync"
and it reported
protocol version mismatch - is your shell clean?
(see the rsync man page for an explanation)
Received signal 16.
That's not the error you're seeing though. I tried redirecting the prompt
to stderr and then it worked after printing the prompt. I then tried
inserting a "read" and it caused it to hang because rsync isn't reading
input from its own stdin to send to its -e command. That still doesn't
sound exactly like what you're seeing but I think it's on the right track.
Maybe you need an option for rsync to pass data from its stdin to the
remote side.
- Dave
