Instead of using the startup script from the above referenced thread, I use the following script on the server (it can run after network-target in startup, or on a recurring basis in cron, which is what I do):Ĭode: export USER=username-you-want-to-run-MC-as So I worked out an alternate solution that has some advantages and some disadvantages over the X forwarding method outlined in the above-referenced thread, and I thought I'd share. I also wanted to (in theory) be able to do some occasional remote fiddling from android devices, and I haven't found any very functional Xserver apps for android. I definitely wanted an SSH-tunneling based solution for security, and the solution from that thread did kind of work for me, but the lag from X forwarding was pretty severe (even on the same LAN), such that it made doing any kind of server-side GUI configuration very difficult and tagging almost impossible. I started out using the X forwarding/SSH method described in that thread for administration, but was having some trouble with it. Given the need to have an active X display to run MC, I figured I might as well try and use the GUI for remote administration as well. This currently requires creating a dummy X display for mediacenter per this thread. So I've been experimenting with running Media Center on a headless server.

Jriver remote access