Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site lsuc.UUCP Path: utzoo!lsuc!dave From: dave@lsuc.UUCP (David Sherman) Newsgroups: net.unix-wizards Subject: Re: killing zombies Message-ID: <754@lsuc.UUCP> Date: Thu, 15-Aug-85 15:21:52 EDT Article-I.D.: lsuc.754 Posted: Thu Aug 15 15:21:52 1985 Date-Received: Thu, 15-Aug-85 15:59:11 EDT References: <368@imsvax.UUCP> Reply-To: dave@lsuc.UUCP (David Sherman) Organization: Law Society of Upper Canada, Toronto Lines: 28 Summary: cu onto the acu equivalent port In article <368@imsvax.UUCP> harris@imsvax.UUCP (Harris Reavin) writes: > Unfortunately no unix wizard on the net had a solution for zombie >processes that disable ports and refuse to die from a "kill -9". I got >mail from a number of other system administrators who had the same problem >and asked for the solution if I found one short of rebooting. We discovered >locally a way to drive a stake through a zombie's heart that I did not >mention in the previous article. It is better than a reboot but is still a >lot of trouble. We disconnect the cable from the controller of the affected >port, change the ttys entry to turn off the port, reconnect the cable, >and reedit the ttys file to turn the port on again. This usually works. >I still hope that someone may come up with a better solution that does >not involve crawling around the back of the computer in search of the >proper cable. I have a solution which works for us here. We have a parallel set of devices called acu* which are the same as tty* except that DCD need not be present to open the device. (I originally installed this kernel mod so as to be able to cu out on a modem line which wasn't supporting carrier detect.) I usually find that doing a "cu -l /dev/acuNN" and out again with ~. will clear the problem. Dave Sherman The Law Society of Upper Canada Toronto -- { ihnp4!utzoo pesnta utcs hcr decvax!utcsri } !lsuc!dave