[comp.windows.open-look] Setting the correct DISPLAY when starting up OpenWindows

jc@raven.bu.edu (James Cameron) (03/25/91)

Running SunOS 4.1.1 with OW2.0
Using the default openwin script to start up X server

The problem:  I can't see how to tell the server that the display I want
              is `hostname`:0.0 instead of :0.0   If I want to run something
              like emacs from the menus, I get a console message stating

	> 	XNeWS Network security violation
	>         Rejected connection from: raven
	> Client is not authorized to connect to server

	      It is obviously the DISPLAY variable.  The openwin script
              is set up to only allow :0.0 and will barf if you (ie, me) 
              try to play with it.  
            
              I tried setting it in .openwin-init but it seems to have no 
	      effect at all.  

Thanks for any help...And I know, this should be in a FAQ, but as of yet, 
I don't believe there is one for C.W.O-L  *8-)  SUN - Care to volunteer
any staff members????   (* grin *) Didn't think so...

JC


--
James Cameron  -  jc@raven.bu.edu        |  "But to risk we must, for the 
Signal Processing and Interpretation Lab |  greatest hazard in life is to risk
ECS Engineering Dept.                    |  nothing.  For the man or woman who
	Boston University, Boston MA     |  risks nothing, has nothing, does
	Work: 617 353-2879               |  nothing, is nothing."
Information Technology                   |
	Boston University, Boston MA     |  (Quote from the eulogy for the late
	work: 617 353-2780 ext. 338      |   Christa McAuliffe.)  

doug@crdgw1.ge.com (Doug Becker) (03/26/91)

    The problem:  I can't see how to tell the server that the display I want
                  is `hostname`:0.0 instead of :0.0

A quick glance through the openwin script shows that it doesn't like any
display specification that doesn't begin with a colon.  If Emacs is trying
to open `hostname`:0.0 when your DISPLAY environment variable is :0.0,
Emacs is broken.  (I use Emacs in an xterm, so I can't tell exactly what's
wrong.)  Are you sure Emacs is linked with the R4 libraries, so that it can
pick up the authorization data correctly?

Probably the easiest way to get Emacs working, if you're not overly
concerned about security, is to do an 'xhost +`hostname`' before you start
emacs.  (You could then do an 'xhost -`hostname`' after it had started.)
Alternatively, you could have the OW 2.0 server start up with authorization
turned off (via the -noauth option to openwin).

-- 

Doug Becker
doug@nmri.ge.com
crdgw1!sane!doug

jc@raven.bu.edu (James Cameron) (03/26/91)

[...Re-posting to clarify things...]

>>>>> On 25 Mar 91 09:22:43 GMT, jc@raven.bu.edu (James Cameron) said:

James> Running SunOS 4.1.1 with OW2.0
James> Using the default openwin script to start up X server

James> The problem:  I can't see how to tell the server that the display I want
James>               is `hostname`:0.0 instead of :0.0   If I want to run something
James>               like emacs from the menus, I get a console message stating

	> 	XNeWS Network security violation
	>         Rejected connection from: raven
	> Client is not authorized to connect to server

James> 	      It is obviously the DISPLAY variable.  The openwin script


The overwhelming response I got was to use the -noauth option upon
startup.  This to me seems like a real bad work around of some
problem.

The DISPLAY variable *should* be set to `hostname`:0 from my understanding;
however, openwin insists that it be :0.0  

I mentioned above that if I run emacs from the menu bindings without the
-noauth option, it can't connect.  The same is true if I try to run it
from an xterm....can't connect until I set the DISPLAY to `hostname`:0

I am only dealing with the terminal that I am on.  I am not trying
to have remote computers pop things up on my screen;  I just want
the things that *should* show up on the terminal show up.  I would
like to have Xdm running openwin, and could set it up right now, but
I will continue with Xsun until I am told of a way to get around
the -noauth problem.

JC

--
James Cameron  -  jc@raven.bu.edu        |  "But to risk we must, for the 
Signal Processing and Interpretation Lab |  greatest hazard in life is to risk
ECS Engineering Dept.                    |  nothing.  For the man or woman who
	Boston University, Boston MA     |  risks nothing, has nothing, does
	Work: 617 353-2879               |  nothing, is nothing."
Information Technology                   |
	Boston University, Boston MA     |  (Quote from the eulogy for the late
	work: 617 353-2780 ext. 338      |   Christa McAuliffe.)  

barnett@grymoire.crd.ge.com (Bruce Barnett) (03/27/91)

In article <656uu7u@openlook.Unify.Com> sane!genmri!doug@crdgw1.ge.com (Doug Becker) writes:


>   If Emacs is trying
>   to open `hostname`:0.0 when your DISPLAY environment variable is :0.0,
>   Emacs is broken. 

The bug is in xnews. Sun knows about this bug.
The bug is the server and has to do with backwards compatability.	

>   Probably the easiest way to get Emacs working, if you're not overly
>   concerned about security, is to do an 'xhost +`hostname`' before you start
>   emacs.


We have a version of emacs that was built using the X11R3 libraries.
It exhibits the same symptom.
	xhost +`hostname`
is the work-around we have used.
--
Bruce G. Barnett	uunet!crdgw1!barnett

jc@raven.bu.edu (James Cameron) (03/27/91)

One last time.....*8-)


(* smile *) Here, let me make the situation completely clear and then
something might be solved....

On the console (a 4/xxx) of raven.bu.edu I want to login in and start 
up OpenWindows.  I don't specify any DISPLAY variable in my .login or
.cshrc files as I might be on a simple vt220 (as I am now *8-) ) 

Once I login and kill of XDM and Xsun (the default Xserver) I can
log in again and run openwin by typing

my-prompt % openwin

Once it is up and running, I do 

% echo $DISPLAY
:0.0
% xhost
raven.bu.edu
% emacs &
XNeWS Network security violation
         Rejected connection from: raven
Client is not authorized to connect to server
[...The above is being sent to my console xterm (ie xterm -C &)]
% setenv DISPLAY `hostname`:0.0  
[...ie setenv DISPLAY raven:0.0]
% emacs &

That works just fine *AND* all other applications including all from
the $OPENWINHOME/bin directory.  That is all work from *that* xterm 
only.

JC

James Cameron  -  jc@raven.bu.edu        |  "But to risk we must, for the 
Signal Processing and Interpretation Lab |  greatest hazard in life is to risk
ECS Engineering Dept.                    |  nothing.  For the man or woman who
	Boston University, Boston MA     |  risks nothing, has nothing, does
	Work: 617 353-2879               |  nothing, is nothing."
Information Technology                   |
	Boston University, Boston MA     |  (Quote from the eulogy for the late
	work: 617 353-2780 ext. 338      |   Christa McAuliffe.)  



--
James Cameron  -  jc@raven.bu.edu        |  "But to risk we must, for the 
Signal Processing and Interpretation Lab |  greatest hazard in life is to risk
ECS Engineering Dept.                    |  nothing.  For the man or woman who
	Boston University, Boston MA     |  risks nothing, has nothing, does
	Work: 617 353-2879               |  nothing, is nothing."
Information Technology                   |
	Boston University, Boston MA     |  (Quote from the eulogy for the late
	work: 617 353-2780 ext. 338      |   Christa McAuliffe.)  

ks@cs.tut.fi (Syst{ Kari) (04/02/91)

In article <656uu7u@openlook.Unify.Com> sane!genmri!doug@crdgw1.ge.com (Doug Becker) writes:

My .xinitrc (yes I have a copy in my $HOME) says:

DISPLAY="`hostname`:0.0"; export DISPLAY

echo "(DISPLAY) ($DISPLAY) putenv" | psh


before starting applications or wm.


--
% This article represents my personal views.
% NeWS flash: "X is the Fortran of windowing systems."
% Kari Systa, Tampere Univ. Technology, Box 527, 33101 Tampere, Finland
% work: +358 31 162585      fax: +358 31 162913      home: +358 31 177412