From owner-freebsd-ports Sat Apr 4 23:58:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11082 for freebsd-ports-outgoing; Sat, 4 Apr 1998 23:58:26 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from jaguar.ir.miami.edu (jaguar.ir.miami.edu [129.171.32.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11076; Sat, 4 Apr 1998 23:58:25 -0800 (PST) (envelope-from marcus@miami.edu) Received: from localhost by jaguar.ir.miami.edu (PMDF V5.1-10 #24029) with SMTP id <0EQX00301KTBWI@jaguar.ir.miami.edu>; Sun, 5 Apr 1998 03:58:23 -0400 (EDT) Date: Sun, 05 Apr 1998 03:58:23 -0400 (EDT) From: "Joe \"Marcus\" Clarke" Subject: Re: 2.2.6, utmp, wtmp, and xterm In-reply-to: <199804050717.XAA01331@ns.frihet.com> To: "David E. Tweten" Cc: ports@FreeBSD.ORG, stable@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I noticed the same problem. I even recompiled XFree86-3.3.2. I also tested it with a variety of window managers and terminals. Eterm seems to be affected as well. I'm sort of leaning towards a bug in X myself, as telnet etc. work fine. Joe Clarke On Sat, 4 Apr 1998, David E. Tweten wrote: > I first noticed this in 2.2.6-BETA, unfortunately not until after the > release. I've since confirmed it with -stable from just a few days ago. The > problem's most likely in XFree86 3.3.2, but I can't be sure since I no longer > have any machines that run anything before XFree86 3.3.2 and post-2.2.6 > FreeBSD. I'm hoping this question will save me having to debug xterm. > > 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 only happens > with ptys that have been used by xterm. Rlogind ptys are okay; so are vtys. > Both /var/run/utmp and /var/log/wtmp claim any pty that ever supported an > xterm is still logged in. Run a last(1) on my machine, and you'll see the > only way an xterm ever gets terminated is by "shutdown". Of course, that's > not true. They terminate quite nicely, requiring only that "logout" be typed > at csh. > > Explicitly setting > > xterm*utmpInhibit: false > > in my .Xresources file changed nothing, so it doesn't seem to be a problem > external to xterm. > > Does this look familiar to anyone, or should I start debugging xterm? I > couldn't find anything about this at the FreeBSD archives (particularly in > the gnats search). Any help would be appreciated. > -- > David E. Tweten | 2047-bit PGP fingerprint: | tweten@frihet.com > 12141 Atrium Drive | E9 59 E7 5C 6B 88 B8 90 | tweten@and.com > Saratoga, CA 95070-3162 | 65 30 2A A4 A0 BC 49 AE | (408) 446-4131 > Those who make good products sell products; those who don't, sell solutions. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-ports" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message