Xref: utzoo comp.unix.questions:32456 comp.unix.admin:2373 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!wuarchive!uunet!cme!durer!rowe From: rowe@cme.nist.gov (Walter Rowe) Newsgroups: comp.unix.questions,comp.unix.admin Subject: Re: Can't kill process! Message-ID: Date: 27 Jun 91 14:22:40 GMT References: <1991Jun24.143454.15728@msuinfo.cl.msu.edu> <1991Jun25.030705.16021@hou.amoco.com> Sender: news@cme.nist.gov Followup-To: comp.unix.questions Organization: National Institute of Standards and Technology Lines: 19 In-reply-to: zwbm07@hou.amoco.com's message of 25 Jun 91 03:07:05 GMT Joe P. DeCello writes: > I have this problem with alot of processes which use /dev/rsx0. > Is there a way to kill this monger without rebooting. Sounds like your process is hung in a device-wait state. What does a `ps ax' show as the status of the process? If its in a device-wait, it will not get the signal until the process returns from some device driver routine (eg. open, close, read, write, ioctl). When executing kernel code, its my understanding that signals are not received until the process exits that code (ie. one of the calls mentioned above completes - there are other calls as well that might cause this problem depending on the circumstances). wpr --- Walter Rowe rowe@cme.nist.gov ...!uunet!cme-durer!rowe National Institute of Standards and Technology / U.S. Department of Commerce