Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!noao!arizona!arizona.edu!cerritos.edu!nic.csu.net!beach.csulb.edu!csus.edu!decwrl!pacbell.com!pacbell!sactoh0!unify!openlook!openlook-request From: lwv27%CAS.BITNET@CUNYVM.CUNY.EDU Newsgroups: comp.windows.open-look Subject: Message-ID: Date: 26 Mar 91 10:26:00 GMT Lines: 48 To: openlook of unify.com at bitnet Subject: Re: Setting the correct DISPLAY when starting up OpenWindows Cc: Bcc: -------- Newsgroups: comp.windows.open-look In-Reply-To: at bitnet Reply-To: Larry W. Virden References: at bitnet Organization: Nedriv Software and Shoe Shiners, Uninc. The syntax being generated for DISPLAY is a proper syntax. From reading the various X reference manuals, for instance the book X Window System C Library and Protocol Reference by Schiefler, Gettys and Newman of MIT page 10 of my edition in the section on "Opening the Display", it is explained that X11 clients use the string in DISPLAY to determine how to open a connection to the server. raven:0.0 means that the toolkit MUST open a TCP socket to the server unix:0.0 means that the toolkit MUST use Unix domain IPC streams. :0.0 means that the toolkit is free to use whatever is faster. on the other hand, when I log into an OpenWindows session and type xhost I am not shown anything. So I have added a: xhost +`hostname` to my .openwin-init file, and do not seem to get the access errors that I occasionally saw before. What is interesting is that very few pgms ever gave me the access error- emacs was one. -- Larry W. Virden UUCP: osu-cis!chemabs!lwv27 Same Mbox: BITNET: lwv27@cas INET: lwv27%cas.BITNET@CUNYVM.CUNY.Edu Personal: 674 Falls Place, Reynoldsburg,OH 43068-1614 America Online: lvirden