Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!spool.mu.edu!cs.umn.edu!ariel.unm.edu!triton.unm.edu!saunders
From: saunders@triton.unm.edu (Richard Saunders CIRT)
Newsgroups: comp.sys.amiga.introduction
Subject: Re: Killing Processes
Message-ID: <1991Apr22.182924.15708@ariel.unm.edu>
Date: 22 Apr 91 18:29:24 GMT
Article-I.D.: ariel.1991Apr22.182924.15708
References: <1991Apr19.122837.1@watt.ccs.tuns.ca> <22253@shlump.nac.dec.com>
Organization: University of New Mexico, Albuquerque
Lines: 30

In article <22253@shlump.nac.dec.com> withers@nitmoi.enet.dec.com (George A. Withers) writes:
>In article <1991Apr19.122837.1@watt.ccs.tuns.ca>,
>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. ... 
...
>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 doesn't seem to work for me in WB2.02.  I started
a shell in the background, and when I attempted to kill it
using the "break" command, it didn't work.  Just to be sure that
everything was okay, I switched to the background shell and typed
a ^C ... and it killed the background shell correctly.  The manual
SAYS that a "break 1" is equivalent to switching to task 1
and hitting CTRL-C.  Since it doesn't appear to work that way,
my guess is that this is one of the perks
of a Beta operating System ;v)

* saunders@triton.unm.edu * "This is _NOT_ Mel Tormet!" - Top Secret