|
OK, here it is... after all that it's actually quite simple. Replace LOCAL and REMOTE below with the hostnames of your local workstation and remote system, respectively (don't get them mixed up!)
On LOCAL:
xhost +REMOTE
. If you use
xauth
you may need to do more than this; see the xauth(1) man
page for more information.
You should consult the
Remote X Apps Mini-HOWTO if you're not familiar with remote X access permission
setup.On REMOTE:
lbxproxy
and tell it to forward to the LOCAL X server,
like this:
$ lbxproxy -display LOCAL:0 :1 &
This tells lbxproxy
to use display :1
on
the REMOTE system; if that system has >1 display already you can use
:2
or whatever instead.
lbxproxy
is providing, instead of the normal display:
$ DISPLAY=:1
$ export DISPLAY
Or, if you use csh or clones:
% setenv DISPLAY :1
xauth
you will need to ensure that your
cookie is available locally. See the
Remote X Apps Mini-HOWTO for more information on this.
That's it; all X apps that are started up pointing to :1
will use
LBX. Of course, there's no reason you couldn't also start X apps
pointing to LOCAL:0
and have both running at the same time.
Hosting by: Hurra Communications Ltd.
Generated: 2007-01-26 17:57:52