From owner-freebsd-current Sat Oct 3 18:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09115 for freebsd-current-outgoing; Sat, 3 Oct 1998 18:57:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09088 for ; Sat, 3 Oct 1998 18:57:54 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA15502; Sun, 4 Oct 1998 11:57:30 +1000 Date: Sun, 4 Oct 1998 11:57:30 +1000 From: Bruce Evans Message-Id: <199810040157.LAA15502@godzilla.zeta.org.au> To: taob@risc.org, wollman@khavrinen.lcs.mit.edu Subject: Re: Processes stuck waiting for tty drain? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Since it was running on a pty, probably something had gone wrong >> with the process on the master side, and so the buffer wasn't >> getting drained. > > Hrm, so this is a telnetd-related problem then? It happened again Probably. I think it's the problem that I tried to debug years ago on freefall. Everything seemed OK except telnetd. ># ps -lfp 5007 > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > 0 5007 148 0 2 0 880 548 select Is ?? 0:06.62 telnetd telnetd is selecting on something instead of reading the pty like it needs to do to drain the pty. This is a telnetd bug unless "something" includes the pty. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message