Xref: utzoo comp.unix.wizards:18493 comp.sys.hp:3076 comp.lang.c:22524
Newsgroups: comp.unix.wizards,comp.sys.hp,comp.lang.c
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: Job Control (a la csh/ksh) from within C
Message-ID: <1989Oct6.164830.5856@utzoo.uucp>
Organization: U of Toronto Zoology
References: <1719@zen.co.uk> <1989Oct3.153120.4750@utzoo.uucp> <320@sopwith.UUCP>
Date: Fri, 6 Oct 89 16:48:30 GMT

In article <320@sopwith.UUCP> snoopy@sopwith.UUCP (Snoopy) 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?

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.
-- 
Nature is blind; Man is merely |     Henry Spencer at U of Toronto Zoology
shortsighted (and improving).  | uunet!attcan!utzoo!henry henry@zoo.toronto.edu