Well I installed the ssh keys to try it out.
I'm still not getting that second password prompt. :-(
(I don't get the first one now either, of course.)
I just get the read error.
I think the shell is executing on the remote side after we complete
authentication. The shell then does its own password prompt - which instead
of receiving a PIN receives a rsync command.
>
> Dave is right, when we use rsync it's with the -e flag and users are simply
> promted for password(s).
> For example we use:
> rsync -vvrtz --delete -e "ssh -l username" --stats \
> --include "*/" --include "*.xml" --include "*.xsl" --exclude "*" \
> --rsync-path=/datastore/rsync/bin/rsync \
> slowlaris:/directory /home/directory
>
> guess it always helps to show the actual rsync execution for clarity ;)
>
> using an expect script or keys will eliminate the first password, you'll
> still have to deal with the SecurID. But like Dave said, there is no reason
> rsync can't handle multiple prompts.
>
> Dave Dykstra 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.
> >
> > - Dave Dykstra
>
> --
> Jason Hammerschmidt - MacLaren McCann Interactive - 416.643.8560
> "He who can no longer pause to wonder and stand rapt in awe, is as good as dead; his
>eyes are closed", Albert Einstein
>
>
>
>
>
--
Rick Otten
[EMAIL PROTECTED]
O=='=++
