Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!bionet!ames!pacbell!sactoh0!unify!csusac!monsoor
From: monsoor@csusac.csus.edu (Matt Monsoor)
Newsgroups: comp.sys.amiga
Subject: Re: Suggestion for kill command.
Message-ID: <1989Oct12.214129.9246@csusac.csus.edu>
Date: 12 Oct 89 21:41:29 GMT
References: <26736@shemp.CS.UCLA.EDU> <7877@cbmvax.UUCP> <1989Oct7.091824.8541@csusac.csus.edu> <32292@auc.UUCP>
Reply-To: monsoor@csusac.UUCP (Matt Monsoor)
Organization: California State University, Sacramento
Lines: 33

In article <32292@auc.UUCP> haj@auc.UUCP (4-Harvey Johnson) writes:
>< . . .  BURP!!  . . .>
>
>In article <1989Oct7.091824.8541@csusac.csus.edu> rohwerwd@csusac.UUCP (W. David Rohwer) writes:
>>
>>I have a suggestion for the next version of the OS.  Can you include 
>>a command to kill a process like the UNIX kill command?  It would make it
>>easier for me to free up resources if a program goes out to lunch.  Also, it
>>would prevent me from doing a warm reboot of my machine. 
>>-- 
>
>I agree!  It  would be nice to stop a process like in UNIX instead of rebooting
>or, as I sometimes end up doing, opening another window while sacrificing
>some memory (thank goodness for multitasking!!!).
>
>Along those lines, a commmand that tells you what processes are running would
>be nice, too.  Sometimes I have processes running that I don't even know about
>or forgot.
>
>
>harve!

Get Xoper from the Fred Fish collection (me thinks its on disk 220)!  It will
allow you to do many things!  I use it to kill processes and tasks when I goof!
I am sorry but I do not have the name of the author with me but he is to be
commended.


-- 
+-----------------------------------------------------------------------------+
|    Matthew G. Monsoor    |    UUPC:     {ucdavis|lll-crg}!csusac!monsoor    |
|      (916) 278-6288      |    Internet:  monsoor@csusac.csus.edu            |
+-----------------------------------------------------------------------------+