Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!eru!hagbard!sunic!news.funet.fi!funic!fuug!demos!avg
From: avg@hq.demos.su (Vadim G. Antonov)
Newsgroups: comp.unix.questions
Subject: Re: kill -9
Message-ID: <1990Oct17.111601.25678@hq.demos.su>
Date: 17 Oct 90 11:16:01 GMT
References: <24788@adm.BRL.MIL> <14166@smoke.BRL.MIL>
Reply-To: avg@hq.demos.su (Vadim G. Antonov)
Organization: DEMOS, Moscow, USSR
Lines: 17

In article <14166@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
>In article <24788@adm.BRL.MIL> frech@mwraaa.army.mil (Norman R. Frech CPLS) writes:
>>I had a process which attached itself to my tape drive and then locked up.
>>I couldn't kill it no matter what I tried.
>Sometimes, playing with the "hung" device (e.g., rewinding the tape, or
>turning off power to the controller) will cause an interrupt that may
>suffice to get the device driver unwedged.

	The simplier method to get an interrupt from the tape controller
	is to load tape, move in forward for some seconds, press REWIND
	and quickly switch drive ON-LINE. When it'd reach the physical
	marker it'll generate interrupt. This trick works as a rule.
	(Anyway the better solution is to hack up driver to make it
	to do timeout-s on operations ;-).

	Vadim Antonov
	DEMOS, Moscow, USSR