Path: utzoo!attcan!uunet!littlei!omepd!mipos3!pinkas From: pinkas@hobbit.intel.com (Israel Pinkas ~) Newsgroups: comp.windows.x Subject: Re: xlsfonts does, sort of, xterm doesn't Message-ID: Date: 9 Apr 89 20:51:38 GMT References: <8904061829.AA07362@dsys.icst.nbs.gov> Sender: news@mipos3.intel.com Organization: Corporate CAD, INTeL Corporation, Santa Clara, CA Lines: 33 In-reply-to: rbj@DSYS.ICST.NBS.GOV's message of 6 Apr 89 18:29:09 GMT In article <8904061829.AA07362@dsys.icst.nbs.gov> rbj@DSYS.ICST.NBS.GOV (Root Boy Jim) writes: > I have more information on what my problem is; UNIX domain sockets. > If I set my DISPLAY to dsys:0 it works fine, but unix:0 dies. > If I use localhost:0 it works too. I saw something like this under X10 when running YP. This happened on Suns with xterm. There was a patch for xterm that fixed this. I'll see if I can find it and send it to you. The problem, as I remember it, was that YP left an extra open file decriptor around. For some reason, xterm assuped that the pip it used to communicate with the process had a fixed file descriptor. You might also be able to find the patch in one of the earlier patches released for X11. Check for anything that patches xterm. The reason that localhost:0 works is that localhost is a synonym for your machine, using the TCP loopback. It is better that using `hostname`:0, but not as good as unix:0. (Many implementation will not put localhost traffic on the ethernet wire, but will put `hostname` packets out there for everybody to see.) -Israel Pinkas -- -------------------------------------- Disclaimer: The above are my personal opinions, and in no way represent the opinions of Intel Corporation. In no way should the above be taken to be a statement of Intel. UUCP: {amdcad,decwrl,hplabs,oliveb,pur-ee,qantel}!intelca!mipos3!cadev4!pinkas ARPA: pinkas%cadev4.intel.com@relay.cs.net CSNET: pinkas@cadev4.intel.com