Remote Window Managers
Lots of times it's extremely frustrating or time consuming to run an xterm on a remote host just to fork your programs from that remote machine. Why not just run your window manager there even though you're not on its console? The window manager is just another X application, after all, isn't it?
Fire off your local X server
xinit /usr/bin/xterm -- :1 &
yields a vanilla X session with merely an xterm running - no window manager. Now you need to add permissions to this window session for the remote host. You can tunnel the connection through SSH if your network is insecure but there's a distinct performance hit. If your network is secure, you can just "xhost +remotehost" and spray directly to your X server:
ssh -fY remotehost /usr/bin/wmaker
or spray directly:
ssh -f remotehost /usr/bin/wmaker -display localmachine:1
The first option, if your remote SSH server supports it, will use a locally defined DISPLAY that then gets tunneled to your local side over SSH. The second option allows remotehost to send X data directly to your local display, then runs WindowMaker there but displaying it locally. Now all your desktop actions are done on the remote machine, not locally.
Our special thanks to Bill from Washington state for this tech tip.
- New Products
- Encrypt Your Dog (Mutt and GPG)
- Practical Tiny Core in the Fire Service
- New Products
- DevOps for Dummies
- Python Scripts as a Replacement for Bash Utility Scripts
- Cooking with Linux - Serious Cool, Sysadmin Style!
- Returning Values from Bash Functions
- Is the Private Cloud a Real Cloud?
- RSS Feeds
Free DevOps eBooks, Videos, and more!
Regardless of where you are in your DevOps process, Linux Journal can help!
We offer here the DEFINITIVE DevOps for Dummies, a mobile Application Development Primer, and advice & help from the expert sources like:
- Linux Journal