Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!ames!ucbcad!ucbvax!ulysses!eric
From: eric@ulysses.UUCP (Eric Lavitsky)
Newsgroups: comp.sys.amiga
Subject: Re: Initial Opinion of Amiga Now: ^C
Message-ID: <1477@ulysses.UUCP>
Date: Wed, 19-Nov-86 12:54:03 EST
Article-I.D.: ulysses.1477
Posted: Wed Nov 19 12:54:03 1986
Date-Received: Wed, 19-Nov-86 22:08:36 EST
References: <939@blia.BLI.COM> <995@cbmvax.cbmvax.cbm.UUCP> <408@ur-cvsvax.UUCP>
Reply-To: eric@ulysses.UUCP (Eric Lavitsky)
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 21


Well, you can't have a kill in the Unix sense, since AmigaDOS processes
don't track resource allocation. Hence, if you tried to kill a process externally, 
you couldn't free up the resources it had allocated (memory, devices etc.). An
AmigaDOS process must free up resources on it's own, therefore it must know how to 
handle ^C or whatever interrupts. If your program is written to handle ^C or ^D, 
^E or ^F, AmigaDOS provides the Break command which is like the Unix "signal". The
format is: Break <process number> <flags>, where flags is a C, D, E or F or any
of C,D,E,F seperated by spaces. This will send the particular signal to any process
(like a background process) and you can pray that the process in question was
written to handle the signal.

Hope that settles the issue,
Eric

-- 

ARPA:	Lavitsky@RED.RUTGERS.EDU
UUCP:	...ulysses!eric
	...caip!topaz!eric
	...hplabs!well!lavitsky