On Wed, Dec 17, 2003 at 04:26:53PM -0600, John Van Essen wrote:
> But ssh has to have *some* opportunity to restore the settings,
> doesn't it?
Not necessarily. One view is that ssh should be catching all fatal
signals during the prompting so that it can be sure to restore the tty
and then die.
On Wed, 17 Dec 2003 02:53:59 -0800, jw schultz <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 17, 2003 at 10:53:22AM +0100, Paul Slootman wrote:
>> On Tue 16 Dec 2003, jw schultz wrote:
>> >
>> > I remember this as well and the root of the problem was not
>> > that rsync didn't wait long enough but that
On Wed, Dec 17, 2003 at 10:53:22AM +0100, Paul Slootman wrote:
> On Tue 16 Dec 2003, jw schultz wrote:
> >
> > I remember this as well and the root of the problem was not
> > that rsync didn't wait long enough but that ssh was not
> > resetting the tty for all catchable signals including
> > SIGUS
On Tue 16 Dec 2003, jw schultz wrote:
>
> I remember this as well and the root of the problem was not
> that rsync didn't wait long enough but that ssh was not
> resetting the tty for all catchable signals including
> SIGUSR1 which is what we send to kill_all children.
Does it make sense to kill
On Tue, Dec 16, 2003 at 03:33:29PM -0800, Wayne Davison wrote:
> On Tue, Dec 16, 2003 at 10:45:12PM +0100, Paul Slootman wrote:
> > I've noticed (at least when using -e ssh) that if ssh prompts for a
> > password or such, and you hit ctrl-c, you're more often than not left
> > with a tty with screw
On Tue, Dec 16, 2003 at 10:45:12PM +0100, Paul Slootman wrote:
> I've noticed (at least when using -e ssh) that if ssh prompts for a
> password or such, and you hit ctrl-c, you're more often than not left
> with a tty with screwed up settings.
Thanks for re-mentioning this patch. It does have the
