On SUSE systems, the ~/.vnc/xstartup script is a little more straightforward: #!/bin/sh xrdb $HOME/.Xresources xsetroot -solid grey xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & twm & Xclient files can start various desktop environments and window managers by using environment variable settings, and they finally fall through to execing the twm window manager (). This enables VNC on Red Hat and Fedora Core systems to follow the same somewhat convoluted chain of X Window startup files that are normally used: ~/.Xclients, ~/.Xclients- $HOSTNAME$DISPLAY, ~/.Xclients-default, and /etc/X11/xinit/Xclients. On Red Hat and Fedora Core systems, the default ~/.vnc/xstartup script simply executes the command script /etc/X11/xinit/xintrc: #!/bin/sh # Red Hat Linux VNC session startup script exec /etc/X11/xinit/xinitrc If this directory and the startup file do not exist the first time you start a VNC server, the directory is created and the startup script is cloned from the default X Window System startup file ( /etc/X11/xinit/xinitrc). The VNC server's startup script is the file ~/.vnc/xstartup. The vncserver script provides a more flexible mechanism for passing arguments to the server, displays status information once the server has started and detached, and also builds in the ability to use a startup script to identify the window manager and any X applications the VNC server should start. The actual VNC server binary, Xvnc, is usually started by a Perl script called vncserver. ![]() Understanding the VNC Server Startup Process Most Linux distributions install one of these VNC implementations as part of their default client/server installations, but you can always obtain the latest version from the appropriate web site. This hack focuses on using TightVNC, although RealVNC is also an excellent choice. TightVNC also features automatic SSH tunneling for security purposes, though any VNC session can be run through an SSH tunnel. TightVNC makes better use of network bandwidth, utilizing JPEG compression for the display and differentiating between local cursor movement and cursor movement that needs to be communicated back to the VNC server. Another extremely popular VNC distribution is TightVNC (), a small, even more highly optimized VNC client and server. VNC is released under the General Public License (GPL), and many of the original VNC developers now work for a company called RealVNC (), which distributes and supports a commercial VNC implementation. ![]() Though VNC exports a graphical environment, the RFB protocol is highly optimized, minimizing the amount of screen update information that must be passed between client and server. VNC uses its own Remote Frame Buffer (RFB) protocol to export graphical changes and handle mouse and keyboard events. ![]() A VNC server is actually an X Window System process that exports an X desktop from the system on which it is running, using a virtual framebuffer to maintain state information about the graphical applications running within that server. VNC follows the traditional client/server model rather than the X Window System client/server model. Similarly, multiple clients can connect to and interact with the same VNC server, providing an excellent environment for training, since many users can view the same desktop. This makes VNC an optimal environment for accessing a graphical console and running graphical administrative and monitoring applications remotely.Īny host system can run multiple VNC servers, each of which exports a separate desktop environment and therefore maintains separate state. VNC servers are typically password-protected and maintain their state across accesses from different clients. A VNC server runs on a desktop or server system and exports an X Window System desktop that can be accessed by a VNC client running on another system. VNC is a cross-platform thin client technology originally developed by Olivetti Research Labs in Cambridge, England, who were later acquired by AT&T. This hack explains how to use VNC to do just that. ![]() You can play around with the standard X Window System DISPLAY environment variable to output programs to different displays, or you can take advantage of cooler, newer technologies such as VNC to display the entire desktop of a remote system in a window on the system on which you're currently working. Virtual Network Computing is the next best thing to being thereand it's cross-platform, too.Ĭommand-line-oriented utilities (such as ssh and telnet) for accessing remote systems are fine for many things, but they don't help much when you need to run graphical utilities on a remote system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |