From owner-freebsd-hackers  Mon Aug 12 00:53:14 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id AAA06726
          for hackers-outgoing; Mon, 12 Aug 1996 00:53:14 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA06721
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 12 Aug 1996 00:53:10 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id RAA01049; Mon, 12 Aug 1996 17:44:17 +1000
Date: Mon, 12 Aug 1996 17:44:17 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199608120744.RAA01049@godzilla.zeta.org.au>
To: bde@zeta.org.au, roberto@keltia.freenix.fr
Subject: Re: Weird pty problem
Cc: freebsd-hackers@FreeBSD.ORG
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>The only  way I've found to  avoid the problem is  to "rm /dev/ttyp8". That
>way, p8 is unavailable and programs skip it...

>Now the state is

>  ttyp8  0   0   0 1296 256     108 OZ   de1580 12923 term

This is more reasonable.  It might be waiting for output to drain,
and something bad has happened to ptyp8.

Does it really only happen for pty #8?

Is ptyp8 open?  (Look for it with fstat or lsof.)

Bruce