hooglant.blogg.se - Vnc connect to current session

#Vnc connect to current session mac os x#
#Vnc connect to current session password#
#Vnc connect to current session windows#

#Vnc connect to current session mac os x#

TurboVNC’s Solaris, Linux, and Mac OS X viewer supports image compression types JPEG or None (RGB). This functionality enables you to reconfigure visual quality and performance on-the-fly.įIGURE B-3 TurboVNC’s Configuration Dialog (Defaults for High Quality Are Shown) You can also press the F8 key after connecting to pop-up a menu (see FIGURE B-3) from which you can select a different connection profile. You can use the -lowqual and -medqual command-line options of vncviewer to switch to the Low Quality or Medium Quality profile, respectively. In the Solaris, Linux, and Mac OS X TurboVNC Viewer, the High Quality profile is the default.

#Vnc connect to current session windows#

This functionality enables you to reconfigure visual quality and performance attributes on-the-fly.įIGURE B-2 TurboVNC Viewer Options Dialog on a Windows Client Or, after connecting to the server, click on the Connection Options button in the toolbar to obtain the same dialog.

Click this dialog’s Options button to select the Image delivery and other attributes, as shown in FIGURE B-2.

In the Windows TurboVNC Viewe r, there are three buttons in the TurboVNC Connection dialog that enable you to easily select the connection profile.

Select the desired connection profile (see FIGURE B-1). In the Java viewer, click the Options button at the top of the browser window.Ģ. You might want to take advantage of TurboVNC’s Lossless Refresh feature. The image quality has very visible artifacts but is still usable. This profile provides optimal performance on low-bandwidth connections, such as broadband. This profile uses about half the network bandwidth of the medium quality profile. Minimize bandwidth consumption at the expense of image quality. Some image compression artifacts, but they are generally minor and not very noticeable. This profile uses about half the network bandwidth of the default profile. Medium-speed networks such as 10 Megabit/second Ethernet. This profile should produce no noticeable image compression artifacts for most applications. Local area network (LAN, 50 Megabit/second or faster). TABLE B-3 describes the three predefined connection profiles, which are alternative tradeoffs of quality versus performance, intended to be chosen based on your network bandwidth. TurboVNC Connection Profiles and Dynamic Quality and Performance Tradeoff Minimize bandwidth consumption at the expense of image quality.Ĭonnect to the VNC server session running on machine host and listening on port port. Improve performance, at the expense of image quality. See Chrominance Subsampling for more information. Once connected, you can change this setting dynamically using the F8 menu. Where s is 1x for no subsampling (4:4:4), 2x for 4:1:1 subsampling, 4x for 4:2:2 subsampling, or gray for no chominance. Set the JPEG chrominance subsampling to s. Once connected, you can change this dynamically using the F8 menu. Where q is a number between 1 and 100 (default is 95).

#Vnc connect to current session password#

The default is to allow any user who correctly enters your VNC password to view your session. Similar to previous scenario, but do not allow others to view or share your session. Note the single colon, as is standard for an X display name. TABLE B-2 Common TurboVNC Viewer ScenariosĬonnect to the VNC server session running on machine host that has an X display number of display. TABLE B-2 describes different scenarios for starting a TurboVNC viewer from a command line. The TurboVNC connection profiles are further described in TurboVNC Connection Profiles and Dynamic Quality and Performance Tradeoff A small GUI (shown in TurboVNC Connection Dialog on a Windows Client) appears to allow selection of a Connection profile. On a Windows host, start a TurboVNC viewer by selecting TurboVNC Viewer in the TurboVNC Start Menu group. The TurboVNC server attempts to use operating system specific techniques to launch the user’s most recently used window manager. If the file does not exist, the TurboVNC server creates one. Upon startup, the TurboVNC server uses $HOME/.vnc/xstartup if the file exists. TurboVNC sessions can only be killed by the user that started the session.

Kill the TurboVNC session of X display number display. Lists all the TurboVNC sessions of the current user on this host. Where the desktop is w x h pixels in size. Start a TurboVNC session with a given virtual desktop size. The X display number of a TurboVNC session is printed out whenever you start the session. Start a TurboVNC session with default settings. TABLE B-1 Common TurboVNC Server Scenarios TABLE B-1 describes different scenarios for the TurboVNC server, the vncserver command, and respective comments. Common TurboVNC Scenarios TurboVNC Server Scenarios