[bug #24268] echo is off in terminal after interrupting the password entry using :ext and ssh

[Derek Robert Price]

Follow-up Comment #4, bug #24268 (project cvs):

The enter-thing might make sense, since CVS as the parent process gets the
first chance to handle the interrupt and its interrupt handler exits
immediately, as opposed to SSH's, which I presume allows the handling of ^C as
input.

Anyhow, you didn't tell me if SSH is still running in the background after
you interrupt CVS?  (`ps -eaf |grep ssh')  My current hypothesis is that
somehow the SSH interrupt handler isn't getting called on your system and that
on other systems we are relying on either automatic pass-through of the SIGINT
after CVS's handler completes or automatic delivery of SIGKILL to children
when the parent process dies.  Then SSH's handler can do the correct terminal
cleanup.

If the SSH process started by your CVS is still running, then that would
verify this hypothesis.  Of course, your SSH could still die without being
given a chance to process any signals.  Not sure how to test that, except to
install a new cleanup handler that delivers a SIGKILL to the child and then
waits for it (with some sort of timeout) before dying.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?24268>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/