Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!seismo!mcvax!inria!axis!mickey
From: mickey@axis.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: System V job control question
Message-ID: <213@axis.fr>
Date: Tue, 7-Apr-87 16:22:10 EST
Article-I.D.: axis.213
Posted: Tue Apr  7 16:22:10 1987
Date-Received: Sat, 11-Apr-87 05:49:53 EST
References: <19@sdeggo.UUCP>
Organization: LERS: soon to be something else!
Lines: 13
Keywords: shl ksh job control
Summary: shl, output control

In article <19@sdeggo.UUCP>, dave@sdeggo.UUCP writes:
> Can anyone explain to me how shl and ksh suspend processes on Sys V without 
> a STOP signal?  Or do they suspend processes at all?  
> 
Your second suggestion was closer. As far as I am aware (having used shl
but never written things using the sxt driver - but having glanced at
the source) all that is done with the non-xurrent processes is to block
their output (this is an option, the default is non-blocked) thus
if the locked output option is chosen (internally this becomes an ioctl)
then as soon as the process writes something to the screen (the sxt device)
it gets blocked and thus de-schedules itself.
	I know nothing about ksh.
			Mickey