From owner-freebsd-current Mon Mar 24 14:53:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA16697 for current-outgoing; Mon, 24 Mar 1997 14:53:36 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA16688 for ; Mon, 24 Mar 1997 14:53:31 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA23808; Mon, 24 Mar 1997 15:40:30 -0700 From: Terry Lambert Message-Id: <199703242240.PAA23808@phaeton.artisoft.com> Subject: Re: 2.2R (src 2.2 211): == dialing To: Anthony.Kimball@East.Sun.COM Date: Mon, 24 Mar 1997 15:40:30 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199703242155.PAA06055@compound.east.sun.com> from "Tony Kimball" at Mar 24, 97 03:55:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > What really bugs me about 3.0 is that children now > get the SIGTSTPs of the parents. If they are the session leader, then this is the correct behaviour. You are supposed to be able to have multiple sessions (jobs) for a given tty. The is, in effect, a "detach and block if output until reattach". One very annoying thing is that even though there is no read, you will get a "stopped" message for a job thrown in the background. This is, I think, a bug in the way job control is being handled (it doesn't do this on my Sun box; the Sun just happily cranks along until input is required, *then* gives the message. Generally, I've got back to it by then. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.