Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ucsbcsl.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!hpda!fortune!amd!decwrl!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!trwrba!cepu!ucsbcsl!discolo
From: discolo@ucsbcsl.UUCP
Newsgroups: net.unix-wizards
Subject: 4.2BSD signal question (revised).
Message-ID: <159@ucsbcsl.UUCP>
Date: Thu, 30-Aug-84 15:56:36 EDT
Article-I.D.: ucsbcsl.159
Posted: Thu Aug 30 15:56:36 1984
Date-Received: Mon, 3-Sep-84 11:08:21 EDT
Organization: U.C. Santa Barbara
Lines: 23

I have solved my own question about why SIGTERM and SIGHUP
continue a stopped process, while the other signals do not.
I quote from the UPM entry for csh(1) pp. 12:

	"kill ...
		... If the signal being sent is TERM (terminate)
		or HUP (hangup), then the job or process will be
		sent a CONT (continue) signal as well."

My new question is why is QUIT not included with TERM and HUP,
since the probable reason this is done is to cause immediate
response to an urgent condition?

Could the reason be tradition?
-- 

uucp: ucbvax!ucsbcsl!discolo
arpa: ucsbcsl!discolo@berkeley
csnet: discolo@ucsb
USMail: Computer Systems Lab
	U.C. Santa Barbara
	Santa Barbara, CA  93106
GTE: (805) 961-3221