Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!aplcen!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.xenix
Subject: Re: Failed kill -9
Message-ID: <1989Dec23.031934.1395@virtech.uucp>
Date: 23 Dec 89 03:19:34 GMT
References: <[628]unix@oldcolo.UUCP> <[628.1]unix;1@oldcolo.UUCP> <822@scorn.sco.COM>
Organization: Virtual Technologies Inc.
Lines: 17

In article <822@scorn.sco.COM>, rogerk@sco.COM (Roger Knopf 5502) writes:
> signal. If you get into one of these routines and can't get out (bug
> or HW failure, its never _normal_), the process will be unkillable
> by any signal. More details can be supplied for those interested.

Just a little bit of nit-picking.

A very normal way of getting into this situation is to go to a 
terminal and cat /etc/termcap.  Once the output starts, do a CTRL-S.
after a few seconds (once the output buffering has filled up) the cat
process will no longer be killable.  However, once a CTRL-Q is typed
at the terminal, any signals sent to the cat process will be delivered.
-- 
+-----------------------------------------------------------------------+
| Conor P. Cahill     uunet!virtech!cpcahil      	703-430-9247	!
| Virtual Technologies Inc.,    P. O. Box 876,   Sterling, VA 22170     |
+-----------------------------------------------------------------------+