On Wed, 5 Jul 2000, Koos Pol wrote:
At 14:12 05/07/00, you wrote:
I work in a multiplatform environment with my home dir being shared between linux, solaris, irix, osf1. In my .bashrc (I use bash on all platforms), I have:
# set X display if we are on remote host if [ -n "$REMOTEHOST" ]; then DISPLAY=$REMOTEHOST:0.0 else DISPLAY=:0.0 fi export DISPLAY
I am not sure what your problem is. If you have a fixed desktop machine and your home directory is auto mounted, you can have a fixed DISPLAY in your .bashrc and you wouldn't need the "DISPLAY=:0.0" part. E.g.: DISPLAY="myhost:0.0"; export DISPLAY You can use this also if you are working om your desktop, as "myshost:0.0" is routed via tcp/ip -> resolver -> localhost. So in effect your X traffic will be routed via the loopback interface.
I *usually* work as a single user on my desktop machine, so your suggestion would work in most cases (and it's what I do). Sometimes I work as a different user on my desktop machine - OK so I could default DISPLAY to my desktop machine. However, if I hard code DISPLAY to my desktop machine - this stops me from working on other machines (the UI will get displayed on my desktop machine). If I soft code DISPLAY to be set (via hostname say), then this also has an undesirable effect - when I remotely login to a linux box, it will try to display the UI locally, rather than from where I logged in from (as REMOTEHOST does not get set). Jamie -- ___________________________________________________________________________ Jamie O'Shaughnessy e-mail: joshaugh@uk.oracle.com Oracle Interactive Television Division phone : +44 118 92 45052 ______________________________________________________ __ __ _ __ . __ Opinions are my own and not those of... (__)|-</-\(__ |__(-_ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq