From owner-freebsd-current Mon Jul 13 12:26:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19903 for freebsd-current-outgoing; Mon, 13 Jul 1998 12:26:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19897 for ; Mon, 13 Jul 1998 12:26:16 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id PAA18581; Mon, 13 Jul 1998 15:26:03 -0400 (EDT) Date: Mon, 13 Jul 1998 15:26:02 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Andrew Gallatin cc: current@FreeBSD.ORG Subject: Re: PF_LOCAL socket problems? In-Reply-To: <13738.22232.735035.745625@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Jul 1998, Andrew Gallatin wrote: > Over the weekend, I built world (and kernel) for the first time in > months. Much to my chagrin, I've had X apps dying with BadLength X > errors all day. The primary offendors are Netscape & Xemacs, which > tend lock up after issuing errors like: I don't get this with netscape, but xmix does it reliably on startup. > The reason I suspect PF_LOCAL sockets is because these problems go > away if I set my DISPLAY to machinename:0.0 rather than :0.0. > As I recall, X apps talk to a server with a display of :0.0 via > PF_LOCAL sockets. Hey, look at that, I set DISPLAY to localhost:0.0 and now xmix works. > Not that it matters, but this is on a 300Mhz PII, running XF86 3.3.2 > (XF86_SVGA atop a 4MB NNidia Riva128 agp video card) 200 MHz PPro here, same X server, but the S3V version. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message