Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!shlump.nac.dec.com!nitmoi.enet.dec.com!withers
From: withers@nitmoi.enet.dec.com (George A. Withers)
Newsgroups: comp.sys.amiga.introduction
Subject: Re: Killing Processes
Message-ID: <22253@shlump.nac.dec.com>
Date: 22 Apr 91 15:44:40 GMT
References: <1991Apr19.122837.1@watt.ccs.tuns.ca>
Sender: newsdaemon@shlump.nac.dec.com
Reply-To: withers@nitmoi.enet.dec.com (George A. Withers)
Organization: Digital Equipment Corporation, Acton MA
Lines: 34

In article <1991Apr19.122837.1@watt.ccs.tuns.ca>,
macauslandr@watt.ccs.tuns.ca writes:
|>From: macauslandr@watt.ccs.tuns.ca
|>Newsgroups: comp.sys.amiga.introduction
|>Subject: Killing Processes
|>
|>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 :-)
|>

Also, if the program supports/traps the BREAK (ctrl-c), you can 
get the Task number by doing STATUS and issue a BREAK n to
that task, as in:

	DF0:> STATUS
	Task 3 loaded as STATUS
	Task 1 loaded as MUSIC_PRG_I_WANNA_KILL
	DF0:> BREAK 1
	DF0:>

This, of course, only works if the program reads the break.

George

 ------------------------------------------------------------------------------
 George A. Withers, Jr.                  |  "There is no life I know to compare
 Digital Equipment Corp., 97 Piper Road  |   with pure imagination.  Living
 Acton, MA   01720   AT&T: 508.264.2339  |   there you'll be free .. if you 
 Addr: withers@nitmoi.enet.dec.com       |   truly wish to be."  - W. Wonka
 ------------------------------------------------------------------------------
      DISCLAIMER:  "Don't look at me!  I didn't do it!" (Krusty the Clown)