Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!uwm.edu!uwvax!tank!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: Job Control (a la csh/ksh) from within C
Message-ID: <20040@mimsy.UUCP>
Date: 7 Oct 89 14:19:25 GMT
References: <1719@zen.co.uk> <1989Oct3.153120.4750@utzoo.uucp> <320@sopwith.UUCP> <1989Oct6.164830.5856@utzoo.uucp>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 20

-In article <320@sopwith.UUCP> snoopy@sopwith.UUCP (Snoopy) writes:
->Henry, Henry, Henry.  Job control is necessary even with a window system.
->Otherwise how does one stop a process without killing it?

In article <1989Oct6.164830.5856@utzoo.uucp> henry@utzoo.uucp (Henry Spencer)
answers:
-One tells the system to suspend it.  Yes, this does require some sort of
-facility for doing so.  No, it does not require mysterious signals with
-bizarre semantics, magic control characters, or any of the other sludge
-that job control brings along.  You've got other windows, remember -- you
-can use one of them to request the suspension, and to fiddle with the
-process thereafter.

How do I get the second window on my H19 here?

One of the things that bothers me about many of these fancy windowing
systems is that there is no way to dial in and use them.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@cs.umd.edu	Path:	uunet!mimsy!chris