You can grep the
output of xdpyinfo (Section 6.2):
blue$ xdpyinfo|grep LBX
13.12
188 Chapter 13: Remote Access
Assuming the LBX extension is present??”it is on most servers, though it may be
dropped from the standard X distribution soon??”you can set up the lbxproxy. This
example sets up the proxy to receive X client connections directed to local display :5,
and to forward the connections to the X server blue:2:
red$ lbxproxy -display blue:2 :5
Once lbxproxy is running, you should direct clients on the remote machine to connect
to the lbxproxy instead of the X server. Setting the DISPLAY variable is the most
convenient way to do this:
red$ export DISPLAY=:5
If you??™re using cookies, you??™ll notice that clients won??™t be able to connect to
lbxproxy, even if they can successfully connect to the X server:
red$ xclock
Xlib: connection to ":5.0" refused by server
Xlib: No protocol specified
Error: Can't open display: :5
This happens because the magic cookie is cross-referenced against the server displayspec
in ~/.Xauthority instead of against the client displayspec. To correct the problem,
make a copy of the server??™s magic cookie (associated with blue:2 in this
example) and cross-referenced it to lbxproxy??™s display number (:5).
Pages:
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292