From owner-freebsd-questions Tue Jun 4 20:57:35 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA21654 for questions-outgoing; Tue, 4 Jun 1996 20:57:35 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA21645 for ; Tue, 4 Jun 1996 20:57:32 -0700 (PDT) Received: from [206.104.22.178] by fly.HiWAAY.net; (8.7.5/1.1.8.2/21Sep95-1003PM) id WAA30911; Tue, 4 Jun 1996 22:57:13 -0500 (CDT) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 4 Jun 1996 22:10:02 -0500 To: questions@freefall.freebsd.org From: David Kelly Subject: couldn't kill -9 kermit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk While messing around with kermit and serial ports I managed to get kermit hung where I can't kill -9 it or nothing. nexgen: {471} ps -l UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 1131 26317 26316 0 18 0 524 392 pause Is p0 0:00.44 -csh (csh) 1131 22837 1 0 4 0 744 868 ttywai IE p1- 0:04.42 kermit -l /d 1131 26353 26352 0 18 0 524 388 pause Ss p1 0:00.40 -csh (csh) 1131 26364 26353 2 28 0 448 264 - R+ p1 0:00.01 ps -l nexgen: {472} The full kermit command was "kermit -l /dev/ttyd3". As I said, was messing around, probably typed "set flow cts", and maybe other things. So now as I write, I've managed to kill the stuck kermit by finding a different RS-232 device to plug into the cable, and cycle the handshake lines. I think when my new device toggled CTS (pin 5) kermit finally quit. It doesn't seem right that a process could block on ttywait and be immune to kill -9. Could probably repeat this situation if it would help. Its likely I didn't originally have a device on the serial cable when I was playing with kermit. -- David Kelly N4HHE, n4hhe@amsat.org, dkelly@hiwaay.net ============================================================= To invent, you need a good imagination and a pile of junk. - Thomas Edison