Path: utzoo!attcan!uunet!ncrlnk!ncrcae!ece-csc!mcnc!rutgers!apple!bionet!agate!brahms.berkeley.edu!koonce
From: koonce@brahms.berkeley.edu (tim koonce)
Newsgroups: comp.os.os9
Subject: Re: Help with OS-9 Kernel
Summary: Sometimes you CAN kill them.
Keywords: condemed process status
Message-ID: <16883@agate.BERKELEY.EDU>
Date: 12 Nov 88 02:46:24 GMT
References: <292@bsovax.UUCP> <834@mcrware.UUCP> <7609@ihlpl.ATT.COM>
Sender: usenet@agate.BERKELEY.EDU
Reply-To: koonce@math.berkeley.edu (tim koonce)
Followup-To: comp.os.os9
Distribution: na
Organization: University of California, Berkeley
Lines: 18

In article <7609@ihlpl.ATT.COM> knudsen@ihlpl.ATT.COM (Knudsen) writes:
>Maybe you can help with a fundamental design problem of OS9.
>There are certain processes that just can't be killed or even
>made to shut down.  Often the XCom9 terminal program will get
>hung because ACIAPAK driver screws up (yes, we all know that
>driver is obsolete and replacements are available).
[Stuff deleted]
>-- 
>Mike Knudsen

One thing I've done several times is to start another copy of XCom9
on top of the old one.  It doesn't start successfully (it hangs
immediately), but after <Break>ing to kill it, both are gone.  It
appears that sometimes attempting to grab the device from under the hung
program dislodges it.  (Maybe the driver recognizes the DEAD status,
anyone know how this works?)

				- Tim Koonce