Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!unmvax!pprg.unm.edu!topgun.dspo.gov!lanl!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: Job Control (a la csh/ksh) from within C
Message-ID: <11233@smoke.BRL.MIL>
Date: 6 Oct 89 21:28:06 GMT
References: <1719@zen.co.uk> <1989Oct3.153120.4750@utzoo.uucp> <15722@duke.cs.duke.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 7

In article <15722@duke.cs.duke.edu> bet@orion.mc.duke.edu (Bennett Todd) writes:
>Job control has more uses than terminal I/O multiplexing.

In fact, there are those among us who think process control is best done
in ways other than by signals generated in response to certain keystrokes.
See the famous "Processes as Files" paper in one of the USENIX conference
proceedings for more about this.