|
|
X Login via XDMCP over an SSH tunnel
You can also run specific apps as needed like xterm or firefox etcl. that reside on the host machine instead of running the entire X session by using those commands instead of Xnest.
One snag I have run into is if you echo $DISPLAY from Terminal.app it returns nothing even if you set $DISPLAY to :0.0 like it should be. You will get something like "xterm Xt error: Can't open display: " from the remote machine. You can get around this one of two ways. 1. Add `DISPLAY=:0.0` before the ssh command. Example: DISPLAY=:0.0 ssh somehost.com2. Run ssh from within X11's xterm. If somebody could fill me in on the difference between how Terminal.app and X11's xterm starts up environment wise that explains why this is happening that would be great :)
X Login via XDMCP over an SSH tunnel
Only children of X11.app will get the DISPLAY variable passed down to it. Terminal.app won't because it isn't a descendent of the X11.app.
Two solutions: Do not set DISPLAY to :0.0 manually or in a script. There is no guarantee that that is the correct value. It can be higher if there is already a lower-numbered X-server running on the machine. Example: start X11.app then fast-user-switch to another user and start X11.app there too. The second user will have DISPLAY of :1.0 instead. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.08 seconds |
|