Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!csd4.milw.wisc.edu!nic.MR.NET!umn-d-ub!rutgers!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Task KILL for Amiga
Message-ID: <5713@cbmvax.UUCP>
Date: 18 Jan 89 04:08:02 GMT
References: <3716@crash.cts.com> <10908@s.ms.uky.edu>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 18

In article <10908@s.ms.uky.edu> sean@ms.uky.edu (Sean Casey) writes:
>In article <3716@crash.cts.com> billk@pnet01.cts.com (Bill W. Kelly) writes:
>>You should be able to terminate the task with a RemTask(task).
>>
>>You will not, however, be able to deallocate its resources.
>
>Hmmm. Why not? Doesn't AmigaDos keep track of owned resources?

	No, not in general.  It can get expensive in memory/spped to do so.

	Also, note that RemTask() of a running process isn't very safe,
unless you know it's doing a Wait(0), or I-looping (Wait(0) is preferred).
If you RemTask something that is in a library call, and has resources locked
(like the layers for the workbench while writing to it), you may end up with
a hung machine.

-- 
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup