Lo que est?y diciendo no es que uses TightVNC; mas bi?n, que trat?s de
ajust?r alg?na configuraci?n de los colores o compression para reduc?r
el datagrama. De esta manera, el programa tendr? una operaci?n mas
optimizada. Tal vez escrib? demasiadas babosadas en el mensaje.

------

I am not telling you to use TightVNC; I am simply suggesting to try to
adjust your color settings and compression options in order to reduce
the size of the datagram. In this manner, the program will be better
optimized. Maybe there was to much noise in my message.

On Thu, 2005-02-03 at 10:53, Andrew Baudouin wrote:
> Si, claro. Gracias.
> 
> Ya trato de instalar TightVNC, no funciona tan bueno como yo quiero.
> 
> 
> On Thu, 03 Feb 2005 10:48:54 -0600, Alvaro Zuniga <[EMAIL PROTECTED]> wrote:
> > I was giving you a hint about performance, is up to you to make yourself
> > a favor and use it.
> > 
> > On Thu, 2005-02-03 at 09:48, Andrew Baudouin wrote:
> > > TightVNC is not the answer.  I do not want to spawn multiple X servers
> > > just to VNC.  I want to VNC into my currently running desktop.
> > >
> > > And Scott, I really appreciate your help thus far.  Good man!
> > >
> > >
> > > On Thu, 03 Feb 2005 09:30:19 -0600, Alvaro Zuniga <[EMAIL PROTECTED]> 
> > > 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.
> > > >
> > > > 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.
> > > >
> > > > good luck.
> > > >
> > > > Alvaro Zuniga
> > > >
> > > > On Wed, 2005-02-02 at 18:22, Scott Harney wrote:
> > > > > Andrew Baudouin wrote:
> > > > > > Is there anyone out there (echoes) who has set up a VNC server to
> > > > > > integrate to their desktop (that will run on their :0 display rather
> > > > > > than setting up new X servers)?  Hopefully with Gentoo experience?
> > > > >
> > > > > Do it all the time.
> > > > > emerge x11-misc/x11vnc (might be masked)
> > > > >
> > > > > http://www.karlrunge.com/x11vnc/ is the home page for the package.  
> > > > > Also
> > > > > look at http://libvncserver.sf.net (emerge net-libs/libvncserver)
> > > > >
> > > > > Here's how I use it:
> > > > > clienthost_xterm_A $ ssh -L 5900:localhost:5900 [EMAIL PROTECTED]
> > > > > remotehost $ x11vnc -display :0
> > > > > (output snipped. x11vnc is now waiting for a connection)
> > > > > clienthost_xterm_B $ vncviewer localhost::5900
> > > > > This connects to your tunnelled ssh port to the remote VNC server
> > > > > running on :0.  Obviously you can use any vnc viewer you are 
> > > > > comfortable
> > > > > with.  You can leave x11vnc running or even run it out of inetd but I
> > > > > don't think either is a good idea for security reasons.  vnc passwords
> > > > > are insecure so the on-demand method I typically use just relies on 
> > > > > ssh
> > > > > for authentication and encryption.
> > > > >
> > > > > Here's another scenario.
> > > > > clienthost_xterm_A $ ssh -L 5900:remote_natted_box:5900 \
> > > > >   [EMAIL PROTECTED]
> > > > > remotefirewall $ ssh remote_natted_box
> > > > > remote_natted_box $ x11vnc -display :0
> > > > > (output snipped. x11vnc is now waiting for a connection)
> > > > > clienthost_xterm_B $ vncviewer localhost::5900
> > > > >
> > > > > So you can ssh to a firewall and crate tunnels to machines behind 
> > > > > them.
> > > > >   Note that this works fine for Windows Term services (TCP port 3389) 
> > > > > as
> > > > > well.  You can tunnel multiple ports to multiple machines.  Just do
> > > > > something like ssh -L5900:host1:5900 -L5901:host2:5900 remotefw .  
> > > > > Then
> > > > > connection vncviewer to the appropriate port on localhost.   man
> > > > > ssh_config to find out how to store these tunnels permanently in a
> > > > > config file so you don't have to type long command lines.
> > > > >
> > > > > Here's another one.  You've got a remote machine that X has died on or
> > > > > you want to fire it up interactively on :0.
> > > > > clienthost_xterm_A $ ssh -L 5900:localhost:5900 [EMAIL PROTECTED]
> > > > > remote $ /etc/init.d/xdm start
> > > > > remote: $ sudo bash
> > > > > remote # x11vnc -auth /var/run/xauth/A:0-oUSh -display :0N
> > > > > (the filename referenced here changes with any running instance of an 
> > > > > X
> > > > > server so just use tab completion within bash)
> > > > > clienthost_xterm_B $ vncviewer localhost::5900
> > > > > You can then disconnect and restart x11vnc as your normal user account
> > > > > after you log in to [x|g|k]dm .  And of course :0 keeps on running so
> > > > > you can disconnect and reconnect as desired both remotely and locally
> > > > > (hint: make sure the sound volume is off  if there are people around 
> > > > > teh
> > > > > remote box :) ).
> > > > >
> > > > > x11vnc is like the X counterpart to the 'screen' terminal application.
> > > > > Very, very useful piece of software.  And it builds and runs anywhere
> > > > > you run X so I've used it on various Linux distros, BSD's and Solaris.
> > > > >
> > > > > libvncserver also has another nifty example piece of software called
> > > > > LinuxVNC which exports the system text tty console over VNC. So yes, 
> > > > > you
> > > > > can execute "startx" on the system console under LinuxVNC, diconnect,
> > > > > then fire up x11vnc to connect to the now running X session.
> > > >
> > > > _______________________________________________
> > > > General mailing list
> > > > [email protected]
> > > > http://brlug.net/mailman/listinfo/general_brlug.net
> > > >
> > >
> > > _______________________________________________
> > > General mailing list
> > > [email protected]
> > > http://brlug.net/mailman/listinfo/general_brlug.net
> > 
> > _______________________________________________
> > General mailing list
> > [email protected]
> > http://brlug.net/mailman/listinfo/general_brlug.net
> >
> 
> _______________________________________________
> General mailing list
> [email protected]
> http://brlug.net/mailman/listinfo/general_brlug.net

Reply via email to