Xref: utzoo comp.unix.wizards:18489 comp.sys.hp:3072 comp.lang.c:22510
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!nosun!qiclab!sopwith!snoopy
From: snoopy@sopwith.UUCP (Snoopy)
Newsgroups: comp.unix.wizards,comp.sys.hp,comp.lang.c
Subject: Re: Job Control (a la csh/ksh) from within C
Message-ID: <320@sopwith.UUCP>
Date: 4 Oct 89 16:00:03 GMT
References: <1719@zen.co.uk> <1989Oct3.153120.4750@utzoo.uucp>
Reply-To: snoopy@sopwith.UUCP (Snoopy)
Organization: The Daisy Hill Puppy Farm
Lines: 20

In article <1989Oct3.153120.4750@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:

| Well, the *proper* way to control jobs is not to fool around with
| abominations like BSD job control, but to do something sensible like a
| window system that lets you interact with multiple processes without
| ornate kludges.  However, that probably isn't what you wanted...

Henry, Henry, Henry.  Job control is necessary even with a window system.
Otherwise how does one stop a process without killing it?

| Nature is blind; Man is merely
| shortsighted (and improving).

Distance != time.

    _____
   /_____\    Snoopy
  /_______\   cse.ogc.edu!sopwith!snoopy
    |___|     sun!nosun!qiclab!sopwith!snoopy
    |___|     uunet!tektronix!tessi!illian!sopwith!snoopy