Ted Gervais wrote:
> > $ export DISPLAY=:0
>
> OK. I will give that a try. I am wondering if maybe something like that
> should be in an environment display file??
NO. That variable needs to be set differently depending upon the
situation, which is why you don't want it to be set statically (like, in
$HOME/.bash_profile for example).
One example of a time when such a thing would trip you up is ssh. You
want ssh to be able to set $DISPLAY dynamically when it connects,
otherwise your forwarded X clients will be trying to connect to an X
server on their local host, probably not what you want.
> And for netcfg - I am root when I try and run that and sometimes I get all
> kinds of funny little errors ending with the '$DISPLAY' question again..
Aha.
What happens when you are _not_ root and you do something like "xclock"
at the command line?
As others (Mikkel, maybe?) have already said, "su -" clears your
environment and runs the startup commands associated with the user whose
id you're adopting (in this case root). So you're starting out with
$DISPLAY set but you don't keep it through the su command. This is
normal, expected behavior.
In these cases you will need to set $DISPLAY manually and also tell your
X server to accept connections from other processes. As mentioned
previously, the "xhost +localhost" command should do this.
--
~~~Michael Jinks, IB // Technical Entity // Saecos Corporation~~~~
We write precisely
since such is our habit in
talking to machines; -- anonymous
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
