From owner-freebsd-stable Sun Apr 5 14:50:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23235 for freebsd-stable-outgoing; Sun, 5 Apr 1998 14:50:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23222 for ; Sun, 5 Apr 1998 14:50:09 -0700 (PDT) (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA24017; Sun, 5 Apr 1998 14:49:45 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <3527FC79.DFD02EC9@san.rr.com> Date: Sun, 05 Apr 1998 14:49:45 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0325 i386) MIME-Version: 1.0 To: "David E. Tweten" CC: stable@FreeBSD.ORG Subject: Re: 2.2.6, utmp, wtmp, and xterm References: <199804050717.XAA01331@ns.frihet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk David E. Tweten wrote: > The presenting symptom is who(1) lists pseudo-terminals as active that are > long since gone. I populate most xterms with a login shell. It's not exactly a solution but I start all my xterms with the -ut switch and I haven't seen the problems you describe, even with 3.3.2. Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message