From owner-freebsd-ports Sun Apr 5 14:26:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16059 for freebsd-ports-outgoing; Sun, 5 Apr 1998 14:26:22 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from ns.frihet.com (root@frihet.bayarea.net [205.219.92.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16015; Sun, 5 Apr 1998 14:25:59 -0700 (PDT) (envelope-from tweten@ns.frihet.com) Received: from ns.frihet.com (tweten@localhost [127.0.0.1]) by ns.frihet.com (8.8.8/8.8.8) with ESMTP id OAA02501; Sun, 5 Apr 1998 14:25:52 -0700 (PDT) (envelope-from tweten@ns.frihet.com) Message-Id: <199804052125.OAA02501@ns.frihet.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Joe "Marcus" Clarke" Cc: ports@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 2.2.6, utmp, wtmp, and xterm From: "David E. Tweten" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Apr 1998 14:25:52 -0700 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org marcus@miami.edu said: >I noticed the same problem. I even recompiled XFree86-3.3.2. Thanks for the information. It's good to know I am not alone. Incidently my entire system (short of Netscape and the like) is compiled locally. >Eterm seems to be affected as well. That would be symptomatic of a problem in 2.2.6-stable, not in the XFree86 3.3.2 version of xterm. If so, rlogind should have the same problem. It doesn't. Strange. -- 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