Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: Bourne shell logout on ^C?
Message-ID: <6477@brl-smoke.ARPA>
Date: Sat, 26-Sep-87 23:43:39 EDT
Article-I.D.: brl-smok.6477
Posted: Sat Sep 26 23:43:39 1987
Date-Received: Sun, 27-Sep-87 11:59:42 EDT
References: <207@minya.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 18

In article <207@minya.UUCP> jc@minya.UUCP (jc) writes:
>When I type a ^C (CTRL-C) on terminal A, I get a new shell prompt.
>When I type a ^C on terminal B, I get a login prompt.

Try the following experiment:
Without changing ANYTHING else, swap the terminals (but not
the connecting cables).  See if the problem follows the
terminal.  If so, it may be dropping DTR when transmitting
^C, or something else equally silly.

>I've run a hex-dump program from terminal B, and it verifies that ^C
>comes in as hex 03, so it's not a transmission error.

This doesn't make sense.  You mean to say that ^C causes logout
only when typed at the shell prompt, but not when typed to some
other program?  According to your stty -a printout, it should
generate a signal (and not appear in the data stream) unless
some program changes the terminal handler modes.