Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site utah-cs.UUCP Path: utzoo!utcs!lsuc!pesnta!hplabs!utah-cs!lepreau From: lepreau@utah-cs.UUCP (Jay Lepreau) Newsgroups: net.unix-wizards Subject: Re: 4.1BSD ^Z/tty mode problem Message-ID: <3202@utah-cs.UUCP> Date: Tue, 12-Feb-85 05:17:44 EST Article-I.D.: utah-cs.3202 Posted: Tue Feb 12 05:17:44 1985 Date-Received: Wed, 13-Feb-85 17:11:20 EST References: <3830@ucla-cs.ARPA> Organization: Univ of Utah CS Dept Lines: 13 1. Yes, this problem exists on both 4.1 and 4.2 and I've seen it (in "ded"). 2. Your analysis is pretty much what I came up with (but not quite so clearly!). 3. I wouldn't really call it a kernel problem, though, because: 4. I solved it in my application by disabling t_*suspc when in a funny tty mode in the child (B). This allows the child to read the ^Z itself, reset its tty modes, and then issue the TSTP to the pgrp, avoiding having the kernel issue the TSTP to the whole pgrp, with the attendant problems. (Note that this problem doesn't occur in raw mode for the same reason my solution works, so all those raw mode screen applications don't see it. Must be cbreak.) Anyone have other ways? Jay Lepreau, lepreau@utah-cs, {ihnp4,decvax}!utah-cs!lepreau