Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!solo.csci.unt.edu!vaxb.acs.unt.edu!news
From: wright@etsuv2.etsu.edu (BRIAN WRIGHT)
Newsgroups: comp.sys.amiga.introduction
Subject: Re: Killing Processes
Keywords: Xoper ARTM
Message-ID: <1991Apr21.223326.46280@vaxb.acs.unt.edu>
Date: 22 Apr 91 03:26:48 GMT
References: <1991Apr19.122837.1@watt.ccs.tuns.ca>
Reply-To: wright%etsuv2.etsu.edu@ricevm1.rice.edu
Organization: NASA-Ames Research Center
Lines: 26
Nntp-Posting-Host: etsuv2.etsu.edu

dtiberio@libserv1.ic.sunysb.edu (David Tiberio) writes...
>macauslandr@watt.ccs.tuns.ca writes:
>>I know this question has probably been address before, but I
>>was wondering how you go about stopping processes which are running
>>in memory from the CLI.  I ran a song executble file the other day and the only
>>way I could get it to stop was by turning off the machine :-)
> 
>  There is a program that does this, but I do not remember the name. It opens
>up a window and scrolls all of the process. You can freeze or kill most
>processes, including devices and stuff. I will find out the name. I wish
>I knew how to FTP or csa.binary the file.

Yes, two of them.  Amiga Real-Time monitor and Xoper.  I believe they are
both written by the same person.  ARTM is a more point and click type thing
and Xoper is more CLI (typing) type.  Both are good, but I think Xoper has
a few more functions than ARTM.  I think Xoper is on Fred Fish and not too
sure about where to find ARTM (maybe ab20?)

>-- 
>    David Tiberio  SUNY Stony Brook 2-3481  AMIGA  DDD-MEN  Tomas Arce 
>           Any students from SUNY Oswego? Please let me know! :)
> 
>                   Un ragazzo di Casalbordino, Italia.

Brian Wright
wright%etsuvax2@ricevm1.rice.edu