From owner-freebsd-current Thu Mar 9 00:24:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA00448 for current-outgoing; Thu, 9 Mar 1995 00:24:41 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA00439 for ; Thu, 9 Mar 1995 00:24:34 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA14322; Thu, 9 Mar 1995 07:33:13 +0100 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id HAA12079 for freebsd-current@FreeBSD.org; Thu, 9 Mar 1995 07:33:13 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.9/8.6.9) id HAA05968 for freebsd-current@FreeBSD.org; Thu, 9 Mar 1995 07:31:00 +0100 From: J Wunsch Message-Id: <199503090631.HAA05968@uriah.heep.sax.de> Subject: Hanging proc waiting for ttyout To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 9 Mar 1995 07:30:59 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1012 Sender: current-owner@FreeBSD.org Precedence: bulk Every now and then, some process hangs in such a state: 107 5766 5765 0 4 0 688 72 ttyout IEs+ p6- 0:02.25 elm In this case, i've accidentally viewed some binary data in this elm, which has been running in a separate xterm (started with xterm -e elm). Somehow the xterm got confues about the garbage, i hit several keys (can't remember all of them :), until the xterm finally went stuck. It didn't accept anything, so i killed the xterm via the window manager. This resulted in the above state, which i've also seen already for processes running on a modem tty, when the modem dropped the line (this has been under 1.1.5.1 though, but the symptoms are identical). There must be some possible deadlock situation when a process is revoked its controlling tty while it is just exiting. Did anyone else see this? Is there any chance to avoid this? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)