![]() To take control of a running X session you will need to configure your VNC server to connect to the same display as X. Last but not the least, you probably don't want to run startkde4 (or any other X session for that matter) over SSH - the network load will likely be quite heavy - VNC will serve you better again. Check whether the X11Forwarding directive is set to yes in your sshd configuration. Without it you can't proceed, because the applications won't know which server to connect to. If for some reason you really want to tunnel X11 through SSH, you must ensure that the DISPLAY environment variable is set up properly by ssh. As an important bonus, since just the inputs and output are forwarded rather than the X protocol itself, network disconnects will just interrupt the session, but all of the programs remain running, which is not the case of X through SSH. Ths also allows you to remotely connect to a running session to help somebody solve a problem remotely. The man page of x11vnc is quite exhaustive and even has a frequently used command line example at the beginning. And of course you probably want to tunnel the transmissionn through ssh or stunnel. You can then use any VNC client to connect to the exported X server. The X server in question can be both a regular one (which outputs to a real display) or a framebuffer based one like Xvfb. ![]() I personally like x11vnc, which connects to a running X server and forwards the inputs/output over the VNC protocol (this can be done as soon the X server is running, so you can interact even with a display manager). In that case VNC is likely to give you better performance, since you can tune the bandwidth/performance requiremens/quality ratios better (this is actually valid for most setups, unless you are on a reliable 100Mbit+ network). If you are using a server-in-the-middle to interconnect two systems, chances are at least one of the lines is rather slow. Is it possible to enable curtain mode for Linux hosts? Chrome remote desktop curtain mac#However the provided instructions for enabling it are only for Windows and Mac with no mention of Linux. To enable Chrome Remote Desktop to prevent someone physically present at a host machine from seeing what a user is doing while a remote connection is in progress The page Control use of Chrome Remote Desktop refers to a "Curtain Mode" which is exactly what I want: This works, but with a major caveat which has prevented me from actually using it: my monitors at the office stay on and the machine is unlocked for anyone to access. #Modify the launch_session() method so it's as follows:ĭisplay = self.get_unused_display_number() #while os.path.exists(X_LOCK_FILE_TEMPLATE % display) I found that I can modify /opt/google/chrome-remote-desktop/chrome-remote-desktop to force a connection to my existing session like so: #Change FIRST_X_DISPLAY_NUMBER to this: ![]() ![]() It's frustrating that, instead of connecting to my existing desktop session (so I can pick up where I left off), it starts a new session upon connecting. I use Chrome Remote Desktop to access my work machine which runs Linux Mint. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |