From owner-freebsd-hackers Mon Sep 25 06:21:07 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA10770 for hackers-outgoing; Mon, 25 Sep 1995 06:21:07 -0700 Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id GAA10744 for ; Mon, 25 Sep 1995 06:21:02 -0700 Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA09008; Mon, 25 Sep 1995 09:20:30 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 25 Sep 1995 09:20 EDT Received: from lakes (lakes [192.96.3.39]) by ponds.UUCP (8.6.11/8.6.5) with ESMTP id UAA13236 for ; Sat, 23 Sep 1995 20:29:10 -0400 Received: (from rivers@localhost) by lakes (8.6.11/8.6.9) id UAA11120 for freebsd-hackers@freebsd.org; Sat, 23 Sep 1995 20:39:21 -0400 Date: Sat, 23 Sep 1995 20:39:21 -0400 From: Thomas David Rivers Message-Id: <199509240039.UAA11120@lakes> To: freebsd-hackers@freebsd.org Subject: That annoying pty problem again... Content-Type: text Content-Length: 754 Sender: owner-hackers@freebsd.org Precedence: bulk I just had the "old" vs. "new" (SIGHUP?) pty problem again. Just to refresh everone's memory, let me know if you've seen this: 1) Start an Xterm... 2) Start 'vi' in that xterm. 3) Shut down the X server, forcing logoff (i.e. CNTL-ALT-BS) 4) Restart the X server 5) Start another xterm - which happens to get the same pty as the one running 'vi' 6) Suddenly, you'll discover that some of your keystrokes are going to that (now supposedly dead) 'vi' session, which is also producing output to your pty (xterm) - along with the shell you have running in your xterm. That is - it would appear that a SIGHUP is getting lost; or the pty driver isn't sending one when the client side is cut off... - Dave Rivers -