Alvaro Zuniga wrote: > Thanks for the great tips Scott. > > I use tightVNC ever since John Herbert recommended this utility about 3 > years ago right in front of the Hunan Restaurant on Sherwood Forest; the > food was great. Went back a few weeks ago to relive once again relive > the moment of my discovery of tightVNC but the quality dropped > tremendously. I still will continue to use tightVNC though.
x11vnc can support the tight encoding from the TightVNC project in addition to the various other methods of optimizing VNC connections. It's primary purpose in life is to provide a VNC connection to your running X desktop rather than spawning a separate desktop for VNC. There are a couple of other vnc servers that provide this -- it's built in to kde for example and I believe gnome has a vnc server available that can do this. > > Anyway, I am not sure what x11vnc is. Due to the name of the client, > vncviewer, I imagine is a derivative of tightVNC. In any case, what I > wanted to mentioned is that you may want to play with the compression > and color settings, look at the man page. The performance is much better > but you must find a balance between beauty and speed. > > I must confess that I get so frustrated with this applications that > sometimes I just drop the ssh tunnel and live in the edge for a little > while and change the password as soon as I am done. In fact, I think > this has become the rule. Scary but then again so is drinking a few > beers at the brlug meetings and driving home immediately after;-) > > An alternative to running a dedicated server is to simply ssh to the box > and launch the vncserver when ever you need it. That what I do. It only > takes me under a minute to get it going. > -- Scott Harney <[EMAIL PROTECTED]> "Asking the wrong questions is the leading cause of wrong answers" gpg key fingerprint=7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5
