Date: Mon, 13 Jul 1998 15:26:02 -0400 (EDT) From: Snob Art Genre <benedict@echonyc.com> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: current@FreeBSD.ORG Subject: Re: PF_LOCAL socket problems? Message-ID: <Pine.GSO.3.96.980713152426.17587A-100000@echonyc.com> In-Reply-To: <13738.22232.735035.745625@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.96.980713152426.17587A-100000>