Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!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
Message-ID: <1991Apr23.054118.46293@vaxb.acs.unt.edu>
Date: 23 Apr 91 10:27:16 GMT
References: <1991Apr19.122837.1@watt.ccs.tuns.ca> <22253@shlump.nac.dec.com>
Reply-To: wright@etsuv2.etsu.edu
Organization: East Texas State University
Lines: 33
Nntp-Posting-Host: etsuv2.etsu.edu

In article <1991Apr22.182924.15708@ariel.unm.edu>, saunders@triton.unm.edu (Richard Saunders CIRT) writes...

[Stuff deleted]

>....
>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)

First, it *SHOULD* be equivalent, but unfortunately the place where the
ctrl-c is intercepted is a different place than the Break command is. This 
means that a program has to poll for that break command or it won't work.
If a certain task has severly crashed it is highly unlikely that a ctrl-c
or a break will do it.  That's the time to whip out Xoper or Amiga Real-Time
monitor and kill it.  If all is functioning correctly ctrl-c or break should
work provided that it can accept both types.  Of course, if it is stated that
it will accept both and doesn't, than obviously it doesn't support both.

Since I am not sure what you are doing, I can't really test it out and give you
an answer to this dilemma in full.  I do have 2.0, though.

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

--------------------------------------------------------------
Brian Wright
wright%etsuvax2@ricevm1.rice.edu   or   wright@etsuvax2.bitnet
--------------------------------------------------------------