tty settings with rsync -e ssh interrupt

[James Manning]

[James Manning]
> best described here:
> 
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=64689
> 
> Confirmed also present with the rpm build at
> http://rsync.samba.org/ftp/rsync/binaries/redhat/rsync-2.4.6-1.i386.rpm

Sorry, also confirmed with rsync-2.5.5 built from source

jmm at jmm /tmp/rsync-2.5.5> rpm -qf $(which ssh)
openssh-clients-3.1p1-3
jmm at jmm /tmp/rsync-2.5.5> ./rsync -e ssh /tmp/foo root at angus:/tmp
root at angus's password: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
jmm at jmm /tmp/rsync-2.5.5>

at that point, the terminal was still in "noecho" mode - simply typing
"stty" and hitting enter confirmed this (note that the command isn't
echoed, I only get the output)

jmm at jmm /tmp/rsync-2.5.5> speed 38400 baud; line = 0;
-echo

Since ssh getting interrupted acts fine (the terminal goes back
to a sane mode), I don't think it's the ssh client.  I confirmed
the behavior after building portable openssh 3.2.3p1 from source:

jmm at jmm /tmp/rsync-2.5.5> ./rsync -e /tmp/openssh-3.2.3p1/ssh /tmp/foo root at angus:/tmp
root at angus's password: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
jmm at jmm /tmp/rsync-2.5.5> speed 38400 baud; line = 0;
-echo

Thanks!

James
-- 
James Manning <http://www.sublogic.com/james/>
GPG Key fingerprint = B913 2FBD 14A9 CE18 B2B7  9C8E A0BF B026 EEBB F6E4